production environment (e.g. App Engine) env vars with workspace dependencies?

[jcamden]

Hello!

I've been working on deploying a full-stack application via Google App Engine. If I try to let App Engine build from source, Google's buildpacks obviously doesn't know what to do with my Yarn workspace dependency urls; so for the client, I just build locally and deploy the static asset. No problem. However, I'm running into an issue when deploying the back-end because, evidently, the server should listen on the App Engine environment's PORT env var. The only way that I can think of to accomplish this is to deploy the source and allow it to be be built via Google App Engine, but, as I mentioned, this is incompatible with workspace dependency urls. I'm sure someone must have experience deploying a node app which depends on both workspace-level dependencies and production-env-scope env vars. Can you give me some direction? Thanks :)

[jcamden]

I just had to listen on port 8081 (that is, build locally with PORT set to 8081 and then deploy the built server). Perhaps 8080 was taken up either the default service (the client, in my case) or perhaps by nginx. I'm not quite sure, but I'm moving on for now.

[jcamden]

Actually, it would be much better not to supply env vars while building, but instead to get them from, you know, the environment. This was a basic dev ops concept which I had not grasped. It was explained to me in comments from jonrsharpe in response to this same question posted on SO: https://stackoverflow.com/questions/67790030/build-with-both-local-yarn-workspace-dependencies-and-production-env-e-g-app?noredirect=1#comment119996587_67790030