Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

By Todd Padwick
Founder of Function & Form
Our node.js Nuxt.js app uses env variables connected with dotenv. When running in dev mode and in production build locally with a standard .env file, our env’s work fine.
In Digital Oceans App Platform, we have added the env variables to the app level env settings and deployed the app:
API_BASE_URL = https://api.example.com
But the env’s dont seem to be working.
In one of our main JS file we have console logged an env as follows:
console.log(process.env.API_BASE_URL);
This log returns the correct env locally both in build and dev mode. But in App Platform, it returns undefined. So this suggests, the unique way in which App Platform handles env variables is not working with our set up (which I would have thought was pretty standard practice with a normal .env file in the root and using dotenv
Does anyone know what else is needed to get Digital Oceans App Platform env variables to work correctly at runtime?
TTTTT TTTTT
90c73a5918cc40f68088aab8502219
56da9fe2b90740cc977f19f9bc88e3
aashaytrivedi1
suchanek-petr
stupidboy
93253b96707848dc9432e5a3c9
BigDarkBlueMantaRay
Valerio C
Valerio C
Dylan192345
GregoryC