On Aug 27, 2009, at 12:08 AM, Nick Quaranto wrote:
Just a note here: I haven't added support for the legacy indexes for
in
Gemcutter. Since you need at least RubyGems 1.3.3 to use the gem
plugins, I
figured supporting the legacy ones shouldn't be a priority as the
project
started. Currently I'm only generating and serving up the modern
indexes
(and these are undergoing some serious refactoring and rework
internally as
well).
It would be interesting to watch the traffic of the legacy indexes
vs the
modern indexes to see if it's even worth it to support those going
forward.
At the very least, we could drop the legacy indexes into S3 and not
update
them.
Here's the full stats for gems.rubyforge.org (not the mirrors, just
the main domain) for Wednesday:
http://infoether.com/~tom/gems.rubyforge.org.logs/usage_200908.html
6K hits on the old-timey yaml index. We only rebuild it once a day...
I should put it up on S3 and do a rewrite rule for just that one file...
Yours,
Tom
_______________________________________________
Rubygems-developers mailing list
http://rubyforge.org/projects/rubygems
Rubygems-developers@rubyforge.org
http://rubyforge.org/mailman/listinfo/rubygems-developers
