Environment variables
Anything your app reads from configuration — connection strings, API keys, feature flags — goes on the site’s Environment tab, not in your repo.
Steps:
- Open the site from Sites, then go to its Environment tab.
- Add each value as a name and a value.
- Deploy (or redeploy) the site for the new values to take effect.
Where they end up: DotDeployer writes them to the server as part of the release, in the shape
ASP.NET Core expects for configuration — your app reads them the same way it would read any other
environment variable or appsettings value, with no code changes needed to work with
DotDeployer.
Security: environment variables are encrypted at rest with a key the API and worker share and the database never holds. They’re never written into your GitHub repo or shown in a deploy log.
Per site, not shared: each site has its own set of environment variables. Two sites on the same server — even two branches of the same repo — don’t see each other’s values.
Changing a value: edit it on the Environment tab and deploy again. The previous release (and its old values) stays on disk until it’s rolled off by the five-release limit, so a bad environment change is a Rollback away like any other bad deploy.
