in that script above you'll see that I --env-file=.env in order to give some ENV. In CI that is provided by the github runners or the digital ocean droplet. What I haven't fixed is the local build without docker. Right now it will be missing ENV if you follow the reasonable path of "build then serve".
Until I can find a fix for both local and docker builds I suggest a workaround.
npm run build
cp .env build/.env
npm run serve:prod
This adds a
deploy.Dockerfilewhich is designed to build a production ready version of the website. It is used by a new github action to auto deploy a [https://cloud.digitalocean.com/apps/edeb5658-aee8-4326-a4cf-6ff6858005fb/deployments?i=023d6b](staging app) to https://staging.blueprintnotincluded.orglocal experimentation
CAVEATS
in that script above you'll see that I
--env-file=.envin order to give some ENV. In CI that is provided by the github runners or the digital ocean droplet. What I haven't fixed is the local build without docker. Right now it will be missing ENV if you follow the reasonable path of "build then serve". Until I can find a fix for both local and docker builds I suggest a workaround.