On Thu, Aug 27, 2009 at 12:21 AM, Nick Quaranto<n...@quaran.to> wrote: > 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. >
CloudFront is a transparent CDN, you only need to subscribe to the service and enable it for the S3 bucket you're using. Then, change the URL to instead of using S3 bucket directly uses the CNAME of the CloudFront enabled bucket. old url: http://my-bucket.s3.amazonaws.com/path/to/my/gem.gem new url: http://assets.gemcutter.org/path/to/my/gem.gem Or something similar. > 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. > Taking in consideration RubyForge has lot of mirrors, collecting real life numbers for it would be really great. -- Luis Lavena AREA 17 - Perfection in design is achieved not when there is nothing more to add, but rather when there is nothing more to take away. Antoine de Saint-Exupéry _______________________________________________ Rubygems-developers mailing list http://rubyforge.org/projects/rubygems Rubygems-developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers
