I am in a similar situation as yours. Thanks to the guy who suggested node-filecache, because, it worked like a charm. N thanks to the guy who suggested lactate too. Although I couldnt get my head around lactate. The Documentation was poor because it was tied down to Express.
But anyways, once again thanks to the guy who suggested filecache, coz he saved my life. :) On Friday, August 3, 2012 3:46:37 PM UTC+1, Felix E. Klee wrote: > > What is a good module to serve some static (JavaScript) files (including > caching and compression)? > > Desired mapping of files to URLs: > > scripts/*.js -> http://example.com/scripts/*.js (only for development) > xyz.js -> http://example.com/xyz.js > app.js -> not served (of course) > package.json -> not served (of course) > ... > > That's it. There is no public directory in my app. > > What I already looked at: > > * node-static: only allows specification of a public directory which is > mapped to the root of <http://example.com/>. As you can see above, > this is not what I want. > > * connect: will not do caching anymore ("connect.staticCache() is > deprecated and will be removed in 3.0 use varnish or similar reverse > proxy caches") > > By the way, I plan to deploy to Nodejitsu. Does anyone know whether they > do automatic caching? > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
