Back
App Hosting // Environment & Secret Files
Environment & Secret Files
Docs › App Hosting
Environment & Secret Files
Keys, tokens and settings your app reads, kept encrypted and given to your app when it starts.
Environment variables
- 1In Hosting, Environment, add a name and a value, or press Paste a .env file and paste one in.
- 2Your app reads them as usual:
process.env.API_KEY,os.environ["API_KEY"]. - 3Changes apply the next time the app starts: a deploy, Restart, or waking up.
.env rulesComments (#) and blank lines are skipped, export NAME=value is fine, values in single quotes are taken as they are, values in double quotes understand \n and can span lines.
NamesLetters, digits and _, not starting with a digit. PORT, HOST, HOSTNAME, NODE_ENV, PATH and HOME are set by NOVA and can't be changed.
LimitsUp to 200 variables, each up to 64 KB.
PrivacyValues are encrypted, shown only masked, never put in NOVA's prompts, and replaced by their names in logs and command output. People you invite to edit the project can run your app, and your app can read them, so invite people you trust.
PlansEvery plan, Free included. Variables you add here are the same ones the workspace's Secrets panel shows.
Set by NOVA
PORTThe port to listen on.NOVA_EXTERNAL_URLYour live app's own address (your custom domain first), for OAuth callbacks and links in emails.NOVA_EXTERNAL_HOSTNAMEThe same address without https://.DATABASE_URLYour database, when NOVA gives your app one (see Database).Secret files
For keys that come as a whole file: a service account JSON, a certificate, an .npmrc for private packages. Upload or paste it under Secret files. Your app finds it at /etc/secrets/<name> and in its root folder (unless your project already has a file with that name). Up to 20 files, each up to 256 KB. Files are written before install, so an .npmrc works for npm install.
A file's contents are not hidden in logs if your app prints them. Don't print secrets.
Join our Discord
Chat with our engineers and become part of the active NOVA developer community.
Need help?
Open an issue on GitHub or email support@bridgeye.com.