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. For a Symfony application this is .env.local, applied on top of the .env your repository commits. 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.
• Workers — on Laravel environments, run queue jobs, Horizon, or a custom background command. See Background workers.
• Storage — how much storage this environment is using, and a quota you can set to cap how large it grows. Only shown on servers that support it. See Storage quotas.

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, and its server is reconfigured straight away so nothing from it keeps running.

A few things to know:

• Production and your only environment can't be deleted on their own. On those, the Danger zone shows Delete application instead, which removes the application with every environment it has. Only the workspace owner can delete an application.
• Databases are kept. The environment's database logins are turned off and the passwords Strackt stored for them are deleted. The databases and their data stay on the server.
• You can't delete an environment while it's busy — finish or wait out a deploy, unlock it after a restore, or contact support if it's paused.
• A billing freeze never blocks a delete. Deleting is one of the ways out of it.

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.