Re: Middleware for serving static files

[Magnus Holm <judofyr@gmail.com>]

On Tue, Dec 20, 2011 at 09:52, Lee Hambley <lee.hambley@gmail.com> wrote:
> Magnus, Rack does, it's Rack::Static… I can't think of a good reason not to
> have a directory like `/s/` to store those assets. Otherwise how should Rack
> know which URLs to route to where? The only information it has is from the
> URL that is requested, and some environmental headers.

Rack::Cascade + Rack::File solves this just fine.

> You'd be well served to consider how you'll solve this problem in
> production, letting your ruby stack serve static files is going to be a
> performance disaster, that's an unspoken rule we all know about, so even
> when you get into production, you're going to need a way to configure
> Apache/Passenger/nginx/unicorn/rainbows to serve these assets,

Yes, in production I'm using Nginx to serve the static, but what about
development?

> and again the
> way will probably be based on a URL filter which will serve assets directly,
> and not proxy them to your application's backend.

Ehm, no? Both Nginx and Apache will serve static files if they exist
in the document root, and proxy to the application backend otherwise.
I just want to mirror this setup in development.

> Final note, I think we're taking the list off-topic, the list is intended
> for Rack developers to discuss and announce changes; I've never seen a
> support thread here, and would recommend stack overflow.

Again: This isn't about solving my problem, it's about making Rack
solve this problem.