I'll take a look into CloudFront, I just haven't yet since the need hasn't come up. My main concern is keeping the gap between publishing a gem and being able to install it low.
As for the costs, I'd like to approach a non-profit organization such as RubyCentral to help deal with them. I originally sent an email out to them first about supporting the project a few weeks ago, but I haven't heard anything back. I'm interested to hear their opinions on the site as well. I would love to get an estimate on bandwidth since the costs are easy to calculate for S3. So far with over 2,000 gem downloads and uploading all of the gems from RubyForge over the past 2 months it's been less than $5. On 8/26/09, John Barnette <jbarne...@gmail.com> 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? > > > ~ j. > > _______________________________________________ > Rubygems-developers mailing list > http://rubyforge.org/projects/rubygems > Rubygems-developers@rubyforge.org > http://rubyforge.org/mailman/listinfo/rubygems-developers > _______________________________________________ Rubygems-developers mailing list http://rubyforge.org/projects/rubygems Rubygems-developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers
