You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Great work on this so far. I have tried a few different ways to get this to deploy to a Node.js flex container in Google Cloud App Engine, but because they use a PaaS architecture, it's not very straight forward (seemingly) to get it to shake hands with the included node/express dist/server. Not sure if you've ever attempted a deploy there, but I feel like I am overlooking something.
My app.yaml is suspiciously simple... perhaps there is some static file juju that I am missing? If you have a spare moment to experiment, would you mind helping me look into this puzzle?
The text was updated successfully, but these errors were encountered:
@dustintheweb You can tell GAE to route server traffic to different files/paths. Here is how I got it to redirect traffic to my prodserver.js file (the entry point for server-side rendering):
@dustintheweb@mklemme I am also trying to deploy this repo on google cloud, can you please let me know how you did, if possible can you share your app.yaml file and changes of package.json SO that I can refer it and develop it on Google cloud.
Great work on this so far. I have tried a few different ways to get this to deploy to a Node.js flex container in Google Cloud App Engine, but because they use a PaaS architecture, it's not very straight forward (seemingly) to get it to shake hands with the included node/express
dist/server
. Not sure if you've ever attempted a deploy there, but I feel like I am overlooking something.My app.yaml is suspiciously simple... perhaps there is some static file juju that I am missing? If you have a spare moment to experiment, would you mind helping me look into this puzzle?
The text was updated successfully, but these errors were encountered: