Hi!  How do I go about setting up a local gem cache?  Every time I've 
googled it in the past (I have firewall issues at work which make this 
something desirable), it's seemed much more complex than I would have 
thought, making me think I'm simply missing something.  I guess it 
really boils down to three questions:

1) How do I (batch) retrieve the gems?

2) Is there any magic to how I "reveal" them to my local network?  
(E.g., HTTP, I assume; is the hierarchy obvious?  Etc.)

3) How do I tell my "gem install", etc., to go and hit up the local 
repo?

Thanks for any pointers...

-Ken


On 2014-12-01 20:41, Jon Hart wrote:
> I got burned by this, just like many other people. While it is
> unfortunate that Rubygems.org was impacted and the nature in which it
> happened appears to be malicious, honestly this is a fairly simple
> infrastructure and tooling problem. It is an infrastructure problem
> in that your application/server/whatever shouldn't be dependent on
> data coming from Rubygems.org, and if it must, then use a local cache
> of Rubygems. It is a tooling problem, IMO, in that things like
> bundler and perhaps even rubygems itself don't make this caching
> functionality on by default.
> 
> -jon
> 
> On Mon, Dec 1, 2014 at 4:57 PM, Rajeev N B <rajeevrvis / gmail.com>
> wrote:
> 
>> Is Still Down.
>> 
>> --
>> Rajeev N B
>> Sent with Sparrow [1]
>> 
>> On Tuesday, 2 December 2014 at 6:25 am, Juanjo Conti wrote:
>> 
>> http://rubygems.org/ [2] is online again.
>> 
>> 2014-12-01 21:24 GMT-03:00 Justin Coyne <jcoyne / justincoyne.com>:
>> 
>> They did.
>> Seehttps://twitter.com/rubygems_status/status/539513292105187328
>> [3]
>> 
>> On Mon, Dec 1, 2014 at 5:59 PM, Juanjo Conti <jjconti / gmail.com>
>> wrote:
>> 
>> Yes. It's because of that. So? The community should be prepare for
>> something like this. Immediately offer a workaround that let people
>> continue working. Am I so wrong in been shock about this silence?
>> 
>> Thanks,
>> 
>> 2014-12-01 20:56 GMT-03:00 Eigil Sagafos <eigil / sagafos.no>:
>> 
>> It's probably the outage/ddos attack at dnsimple. They're
>> supposedly close to a fix.
>> 
>> Eigil
>> 
>> 
>> Sent from Mailbox [4]
>> 
>> On Tue, Dec 2, 2014 at 12:53 AM, Juanjo Conti <jjconti / gmail.com>
>> wrote:
>> 
>> Any alternative or workaround for this problem?
>> 
>> --
>> 
>> Juanjo Conti
>> Mi primer novela ya se puede conseguir en:
>> http://www.juanjoconti.com.ar/xolopes [5]
> 
> --
> 
> Juanjo Conti
> Mi primer novela ya se puede conseguir en:
> http://www.juanjoconti.com.ar/xolopes [5]
> 
> --
> 
> Juanjo Conti
> Mi primer novela ya se puede conseguir en:
> http://www.juanjoconti.com.ar/xolopes [5]
> 
> 
> 
> Links:
> ------
> [1] http://www.sparrowmailapp.com/?sig
> [2] http://rubygems.org/
> [3] https://twitter.com/rubygems_status/status/539513292105187328
> [4] https://www.dropbox.com/mailbox
> [5] http://www.juanjoconti.com.ar/xolopes