Manage project environments

Project environments identify where an activity or maintenance event happened, such as Production, Staging, or a preview site. They make the project activity feed and reports easier to understand without creating separate DeployMonitor projects for each target.

Understand the Production environment

Every project has a primary Production environment. DeployMonitor creates it automatically and keeps its URL synchronized with the project's URL in Project > Settings > General.

The primary environment cannot be deleted. Change the project's URL in General settings when the Production URL needs to change.

Create an environment

Project Developers and Administrators can create environments:

1. Open the project.
2. Select Settings, then Environments.
3. Select New environment.
4. Enter a descriptive name, such as Staging, and its URL.
5. Save the environment.

DeployMonitor generates a URL-friendly slug from the name. Each active environment in a project must have a unique slug and normalized URL.

Environments do not create additional uptime monitors. The project's monitor continues to check the primary project URL. Environments are used to classify project logs and maintenance records.

Delete an environment

Only a project Administrator can delete a non-primary environment. Open Settings > Environments, find the environment, and choose its delete action.

Deleting an environment prevents it from being selected for new activity. Existing logs and maintenance records retain their historical environment association. The primary Production environment cannot be deleted.

The current interface supports creating and deleting non-primary environments, but it does not edit them. If a non-primary environment's details are wrong, an Administrator can delete it and create the correct environment while historical records retain the old association.

Troubleshooting

• Environments is missing from Settings: project Members cannot manage environments. Ask an Administrator to change your role if appropriate.
• You cannot delete an environment: only Administrators can delete, and Production is protected.
• The name or URL is rejected: use a distinct name and URL that are not already active in this project.
• A log is not assigned: choose the environment explicitly when creating the log, or use a source URL matching the environment URL.