Environment settings

The Settings tab gathers everything you can change about a single environment. Open an application, pick the environment from the switcher, and choose Settings. Each section here has a focused guide of its own — this page is the map.

What you can change

• Secrets — the API keys, tokens, and other values your app reads at runtime. Values stay masked; to change one you enter a replacement. See Manage environment variables.
• Configuration file — the .env template strackt fills in at deploy time, with autocomplete for your service and secret values. See Edit your config template.
• Domains — the addresses this environment answers on. Add your own custom domain, remove one, or toggle the free strackt address. See Domains and SSL.
• Bound services — the databases and caches this environment uses. Connect an unbound requirement to a service, or disconnect one. See Add a service.

Each of these is scoped to the environment you're viewing, so a change to staging never touches production until you make the same change there.

Deleting an environment

At the bottom is the Danger zone, where you can delete the environment you're viewing. Deleting is permanent — the environment and its settings are removed.

A few things to know:

• Production can't be deleted. It's the permanent home of your live application.
• You can't delete an environment while it's busy — if it's mid-deploy, paused, or otherwise locked, the action waits until it's settled.

Most changes you make here queue a pending change that applies on the environment's next deploy, so you'll often see a reminder that a deploy is needed to put your changes live.