bellycard / napa

A simple framework for building APIs with Grape
Other
329 stars 72 forks source link

Serving static files #227

Open ashtonthomas opened 9 years ago

ashtonthomas commented 9 years ago

Do we have a preferred manner for serving static files? Should we have something like this built in: https://github.com/alexmamonchik/napa-skeleton/blob/master/lib/middleware/static_files.rb

shaqq commented 9 years ago

usually from S3

ashtonthomas commented 9 years ago

I'm playing with napa on a side project (on an app that will have very little load), and I plan on just serving a single page app from the /public folder. I was thinking we may want to support some wrapper around Rack::Static just to make this easier for others using napa.

@shaqq, do you think it's worth including this in napa?

heymackey commented 9 years ago

I like this idea. Would be nice for SPA that have a Napa backend.

shaqq commented 9 years ago

Hm. Yeah. I wonder how Napa would best fit in the world of developing SPA's. At Belly we use S3 to serve basic assets. So, I don't have a better answer than "Rails, shrug?"

I suppose I'm indifferent on adding this to Napa, yet knowing that there's most likely a larger architectural decision at play.