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 handlers in app.yaml, though, and just duplicates them via express in
app.js instead. that's ok, but it's unfortunate for larger applications
with many different static file handlers in app.yaml, since you have to
duplicate them all, and they'll inevitably skew when you change them.
if this is expected, i'm happy to file a feature request on the issue
tracker! just let me know.
On Thursday, July 12, 2018 at 9:20:30 AM UTC-7, Kenworth (Google Cloud
Platform) wrote:
>
> This is currently possible. Here is an example to help you get started:
>
>
> https://github.com/GoogleCloudPlatform/nodejs-docs-samples/tree/master/appengine/static-files
>
> npm start app.standard.yaml
>
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-appengine/60e8d17a-61b1-4bf7-aced-f669092fcbf6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
