It's working for me...
% gem fetch RedCloth -Vv 4.2.0
GET 200 OK: http://gemcutter.org/specs.4.8.gz
Downloading gem RedCloth-4.2.0.gem
GET 302 Moved Temporarily: http://gemcutter.org/gems/RedCloth-4.2.0.gem
GET 200 OK:
http://s3.amazonaws.com/gemcutter_production/gems/RedCloth-4.2.0.gem
It did work for me a couple of hours later. It had also failed several
times before I posted.
I think the issue is consistency - random gems (not always redcloth)
were failing to install with the error message - http://
gemcutter.org/ does not appear to be a repository - which in the
example
Just a thought.
Are the requests to gemcutter using HTTP?
Is the system using ETags / If-Mod-since?
Seems there could be a way to use a forward proxy to gemcutter.
It would help out:
1) less bandwidth for both gemcutter and heroku
2) faster image build times on heroku
3) less load on the
Yes, we are.
http://github.com/qrush/gemcutter/blob/master/app/metal/hostess.rb#L13-34
-Nick
On Mon, Nov 2, 2009 at 1:17 PM, Keenan Brock kee...@thebrocks.net wrote:
Just a thought.
Are the requests to gemcutter using HTTP?
Is the system using ETags / If-Mod-since?
Seems there could be a
