Deployments overview
Day-2 operations for Services: deploy, scale, route traffic, observe logs, and protect data.
This section covers day-2 operations: what you do after a Service exists in an Environment. Work happens mostly inside a Service in the Applications flow: tabs for Deployments, Logs, Scaling, Domains, Volumes, Proxy, and related settings.
For terminology, read Deployments and Services under Core Concepts in the sidebar.
What you can do here
Open the matching page from Deployments and Operations in the sidebar (same order you see there):
| Topic | Typical goal |
|---|---|
| Redeploy and rollback | Ship changes or recover from a bad release |
| Logs | Inspect build, deploy, and runtime output |
| Environment variables | Change config and roll it out safely |
| Scaling | Adjust replicas and resource defaults |
| Volumes and persistent storage | Keep data across restarts |
| Proxy and routing | Tune reverse-proxy behavior |
| Domains and SSL | Custom hostnames and certificates |
| Backups | Protect database Services |
| Health checks and runtime behavior | How status, queues, and restarts behave |
| Operational best practices | Habits that reduce incidents |
Database Services use a shorter tab set (Overview, Logs, Deployments, Backups, Settings). App and Docker Services add Variables, Scaling, Domains, Volumes, and Proxy.
When something goes wrong
Start with Troubleshooting overview under Troubleshooting in the sidebar, then open the symptom page that matches (for example Deployment issues or Domain and SSL issues) from Troubleshooting in the sidebar.
Screenshots
Illustrations for this overview are optional. Task pages in this section include
a Screenshots subsection listing recommended captures. Authors store files
under packages/docs/assets/ and reference them in MDX as /docs-assets/...
with meaningful alt text, per the documentation program screenshot policy.