Re: [google-appengine] Re: Run Node app locally and serve static file handlers from app.yaml?

thanks, steren! makes sense. i'm actually trying the Node runtime for the first time, on a small personal project, so i don't actually have the "lots of static file handlers in Node" use case yet. i'm just sensitive to DRY and seeing duplicated things skew over time. thanks again! On Thursday

Re: [google-appengine] Re: Run Node app locally and serve static file handlers from app.yaml?

Hi Ryan, The feedback we receive was that Node.js developers expect to start their application with "npm start" more than with "dev_appserver.py". Replicating the handlers in your web framework is indeed the recommendation that we give in our static handler documentation

[google-appengine] Re: Run Node app locally and serve static file handlers from app.yaml?

thanks, kenworth! looks like the key part of that example is these lines in app.js: // Use the built-in express middleware for serving static files from './public' app.use('/static', express.static('public')); that does indeed get the static files serving. it still ignores the static file hand

[google-appengine] Re: Run Node app locally and serve static file handlers from app.yaml?

This is currently possible. See example . -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving ema