On Aug 26, 2009, at 14:57 , John Barnette wrote:
Nick,
On Aug 26, 2009, at 1:42 PM, Nick Quaranto wrote:
1) Redirect gems.rubyforge.org to gemcutter.org for gem serving.
(all gems
are currently mirrored from RubyForge and are ready for consumption)
RubyForge currently has a pretty good mirror system for supporting
Gem downloads. I expect Tom could get your some figures on how much
bandwidth they use. If Gemcutter was the default RG source, how
would you deal with this? Are you planning on eating S3 costs
yourself? Are you thinking about using something like CloudFront,
since S3 itself isn't strictly a CDN?
(possibly) even better, I'm pretty sure we could get Tom convinced
that gemcutter is a good idea and we should migrate rubyforge to it.
_______________________________________________
Rubygems-developers mailing list
http://rubyforge.org/projects/rubygems
Rubygems-developers@rubyforge.org
http://rubyforge.org/mailman/listinfo/rubygems-developers
