Deployments

Application deployment within Salus involves a structured process for releasing software updates, changes, or new features to various environments. Salus’ deployment functionality is seamlessly integrated within its CI/CD pipelines. These pipelines automate the steps required for building, testing, and deploying applications, resulting in consistent and repeatable processes.

You can view existing and active deployments on the deployments page of each project in your workspaces.

Deployment Summary

Each card on the left-hand panel provides a quick overview of your configured environments and a snapshot of how your most recent or current deployments are performing.

Release Status

• Release active means that there are recent releases that have been made into that environment
• No release yet means, since the day this environment was configured no releases have been made

Domains

You can grab quick links for salus or your own custom domains to easily access your latest deployment.

If no custom domains have been configured, the link will be automatically available on the card.

Deployment Info

• Status
• Trigger date
• Branch or tag deployed to

Deployment Detail

For all environments with active releases, the detail view shows what’s running and how it’s set up:

• The release — the deployed commit, with a link to it, and who triggered the deployment.
• Networking — whether the deployment is public or private, its port, the public URL and any custom domain, and its private DNS name.
• Resources — the memory and CPU sizes it runs with, and its minimum/maximum instance counts.
• Associated pipeline details and the Automated Deployment status.

Deployment history and rollback

Each environment keeps a history of its deployment revisions, so you can see what was released and when — and roll back when a release causes trouble. See Deployment History & Rollback.