From: Tom Copeland <tom@...>
Date: 2008-06-27T12:26:47+09:00
Subject: Re: Rubyforge RubyGem propagation delay


On Fri, 2008-04-25 at 08:07 +0900, Ryan Davis wrote:
> On Apr 23, 2008, at 18:47 , Tom Copeland wrote:
> 
> > Another option is for RubyForge to just serve up gems for the first 24
> > hours or so after they're released.  Jeremy Kemper did some nice  
> > rewrite
> > rules for this:
> >
> > http://rubyforge.org/tracker/index.php?func=detail&aid=14803&group_id=5&atid=104
> 
> I have a clean and simple 404 handler written in ruby that allows for  
> pattern matching and redirection. Such a thing could easily be used by  
> the mirrors to throw back at rubyforge.

I just added these rewrite rules and wrote some PHP code to populate the
file that the RewriteMap reads... that should cut the deploy time down
to the gem index rebuild interval (currently 30 minutes)...

Yours,

tom