[Rubygems-developers] Mirror fallbacks (was: rubygems.orgdown ?)

Berger, Daniel Daniel.Berger at qwest.com
Mon Jan 28 15:22:46 EST 2008


> -----Original Message-----
> From: rubygems-developers-bounces at rubyforge.org 
> [mailto:rubygems-developers-bounces at rubyforge.org] On Behalf 
> Of Jeremy Hinegardner
> Sent: Monday, January 28, 2008 1:17 PM
> To: rubygems-developers at rubyforge.org
> Subject: Re: [Rubygems-developers] Mirror fallbacks (was: 
> rubygems.orgdown ?)
> 
> On Mon, Jan 28, 2008 at 01:57:04PM -0600, Berger, Daniel wrote:
> > > -----Original Message-----
> > > From: rubygems-developers-bounces at rubyforge.org
> > > [mailto:rubygems-developers-bounces at rubyforge.org] On Behalf Of 
> > > Jeremy Hinegardner
> > > Sent: Monday, January 28, 2008 11:09 AM
> > > To: rubygems-developers at rubyforge.org
> > > Subject: [Rubygems-developers] rubygems.org down ?
> > > 
> > > I'm getting a 503 Service Temporarily Unavailable from 
> rubygems.org.  
> > > Is this a planned outage?
> > 
> > Is there a way to configure rubygems to fallback to a mirror in the 
> > event of an error like this?
> > 
> > With Perl's CPAN, for example, you select a bunch of 
> mirrors the first 
> > time you run the CPAN shell. From then on, if there's a problem 
> > downloading from your first selection it defaults to the 
> next mirror, 
> > and so on, until it either succeeds or goes through all of 
> your mirrors.
> > 
> > Can we do that? If so, how?
> 
> Correct me if I'm wrong, but rubygems.org is not where the 
> gems are distributed.  They are hit via gems.rubyforge.org. 
> Those two addresses resolve to different IP's.  rubygems.org 
> is the documentation.
> 
> enjoy,
> 
> -jeremy

Oh, geez, I misread that.

But, I'm still curious about my original question. :)

Thanks,

Dan 


This communication is the property of Qwest and may contain confidential or
privileged information. Unauthorized use of this communication is strictly 
prohibited and may be unlawful.  If you have received this communication 
in error, please immediately notify the sender by reply e-mail and destroy 
all copies of the communication and any attachments.


More information about the Rubygems-developers mailing list