Environment variables
Store named values in the project's environment section for executed commands, such as a database address or application mode.
Add and edit
- Open the project environment and add a row.
- Enter a unique name containing letters, digits and underscores, beginning with a letter or underscore.
- Enter its value and save.
- Enable passing saved variables in the deployment, process or scheduled task configuration when needed.
For example, APP_ENV may have the value production. Your application determines the actual names and values.
How values are used
Values are passed as process environment variables. No .env file is created automatically. If your application requires one, prepare it separately or adjust how it loads configuration.
New values apply on the next configured execution. An already running process does not automatically receive them; reapply its configuration and verify execution after changes. Follow your application's requirements for any configuration cache as well.
Removal and sensitive values
Removing an already saved row immediately deletes that variable from the stored environment. Check whether scripts or processes use it before removal.
Variables may contain passwords. Keep them out of public examples and support reports, and restrict server sharing to people who should access this configuration.