What should Raptor do about assets?

[garybernhardt]

Tom, when you asked "Should raptor include asset serving itself?", are you asking about simply serving a public directory, or are you asking about fancy asset pipeline stuff like the changes in Rails 3 that I don't understand?

[tcrayford]

Yes

Both of those (but seperately)

[garybernhardt]

What do Sinatra folks do?

[tcrayford]

Often times (from what I can see in their docs, and from experience), they'll write an action of their own that directly serves assets (and e.g. compiles coffeescript on the fly) for development mode. By default, sinatra just serves all files under /public by default.

I think serving stuff out of public is good enough for me for now (I can compile sass by myself)

[tcrayford]

Looking at sinatra's source code, they inlined the static serving into the framework (probably for speed).

[garybernhardt]

I think that's a reasonable thing to do: mount some Rack app to serve static content.

[tcrayford]

In raptor right? I can probably send a pull request soon.

[psyho]

how about Rack::Static? Isn't that good enough?

[tcrayford]

We probably want Rack::File instead of Static, at least as I see it.