Configure environment variables and secrets | NodeFlux.eu Docs
Keep bot tokens, API keys, and connection strings out of your source code.
Steps
- List the configuration values your application needs, such as PORT, BOTTOKEN, DATABASEURL, or a signing secret.
- Add them through the service configuration or startup environment controls available in the manager.
- Restart the service after changing configuration, then confirm in logs that required values are present without printing the values themselves.
- Rotate a secret immediately if it was committed to a repository, pasted in chat, or shown in a screenshot.
Notes
- Use a separate secret for each application and environment.
- A .env file can be convenient for local development, but it must stay out of version control and be protected like a password.
Warning
Never send tokens, API keys, passwords, or full database connection strings to support unless a secure support process specifically requests them.
Related NodeFlux pages
- Make a Node.js web app reachable — Bind an Express, Fastify, or similar app to the service port provided by the panel.
- Connect a Node.js app to an external database — Use an external database safely without assuming NodeFlux provides a managed database for customer apps.
- Deploy a Node.js application from files — Upload a small Node.js project, install its dependencies, and start it safely.