Deployment guide
Environment variables in Deploy Hatch
Keep runtime configuration separate from source code and provide the values your deployed application needs.
Free beta · one project · no credit card required
GitHub to running workload.
A short path from source code to something you can operate.
Connect GitHub
Sign in, connect your GitHub account, and choose the repository you want to run.
Configure and deploy
Deploy Hatch detects common runtime settings and gives you control over build, start, revision, and environment configuration.
Keep it running
Watch deployment and application logs, then restart, stop, redeploy, or open public web workloads from the dashboard.
What belongs in environment variables
Use environment variables for configuration that differs by environment or should not live directly in source code: API credentials, bot tokens, service URLs, feature configuration, and similar runtime values.
Do not commit secrets
Keep sensitive values out of Git history. A .gitignore entry does not remove a secret that was already committed; rotate exposed credentials at the provider when necessary.
Configure the project
Use the project environment-variable interface in Deploy Hatch to add and manage the values required by the workload.
Be careful with logs
Applications can accidentally print environment values. Treat application logs as operational output and avoid logging credentials or secret-bearing objects.
Put a real workload through it.
Connect GitHub, deploy, and see whether the workflow fits your project.