> At the moment though I am not able to load Ramaze::Rewrite.

> I have tried

> require 'ramaze'
> require 'ramaze/route'

> However I get this error

> ./start.rb:9: uninitialized constant Ramaze::Rewrite (NameError)

> I've also tried cloning the git repository and calling the files
> directly

> require File.dirname(__FILE__) + '/../vendor/ramaze/lib/ramaze.rb'
> require File.dirname(__FILE__) + '/../vendor/ramaze/lib/ramaze/
> route.rb'

> However I get this error

> undefined method `path_rewrite='

> I'm sure I'm being ignorant, but I've been playing around with
> different require combinations but I can't seem to load
> Ramaze::Rewrite

> On May 10, 12:43 am, "Aman Gupta" <themastermi...@gmail.com> wrote:

> > Rewrite rules are now evaluated before the file dispatcher:http://github.com/manveru/ramaze/commit/de363b2a83997c12f54c28ce8c356...
> >   Aman Gupta

> > On Sun, May 4, 2008 at 5:37 PM, ara.t.howard <ara.t.how...@gmail.com> wrote:

> > > On May 4, 2008, at 5:24 PM, Aman Gupta wrote:

> > > > Agreed, the only issue is that those rewrites will be ignored if you
> > > > setup nginx/lighty/apache in front of your ramaze instance to serve
> > > > static files. That's probably fine though... it's your job to
> > > > replicate those rewrites in your front-end proxy.

> > > yup, exactly.  no way around it i think - if you have crazy complex
> > > static serving, like for a site of sites, you would indeed have to
> > > replicated that logic or just let ramaze do it.  ramaze does it very
> > > well know, with minimal pain.  but easier is always better ;-)

> > > a @http://codeforpeople.com/
> > > --
> > > we can deny everything, except that we have the possibility of being
> > > better. simply reflect on that.
> > > h.h. the 14th dalai lama