Deployment Management: all deployments
Deployment Management is where you deploy your app into a cloud account of your own (DigitalOcean, AWS, Google Cloud or Microsoft Azure) and keep track of every deployment made for it. This page covers the list of deployments. To create one, see Deploy your app to a cloud account.
Deployment Management or Deploy? They do different jobs. The Deploy page (Deployment steps in detail) shows the steps Dalfin runs to publish your app on Dalfin's own hosting. Deployment Management puts a copy of your app on servers in your own cloud account, and you pay that cloud provider for them.
Before you start
- This page is meant for team admins.
- To deploy anything, the app needs a published build. See Publish your app.
- To remove a deployment, you need credentials for the cloud account it runs in. Dalfin never keeps them.
Steps
Open Deployment Management
Open your app and select More, then Deployment Management (just below Deploy). The chat and build history stay on the left, and View Live App and the Published menu stay in the top bar for the version Dalfin hosts.
The page opens on All deployments: "Monitor every deployment across services, providers and environments." Select New deployment at the top right to start the deployment wizard.
Read the deployments table
Each deployment is one row, newest first. The columns are:
| Column | What it shows |
|---|---|
| Deployment ID | The app's hostname if it has one, otherwise the run ID or the deployment's own ID, followed by how long ago it last changed, for example "· 17 h ago". |
| Model | How the app runs, for example a Droplet or an EC2 instance. |
| Status | A coloured badge (see Statuses below). Hover over it for more detail. |
| Provider | DigitalOcean, AWS, Google Cloud or Microsoft Azure. |
| Region | Where the servers run. Shows "—" when the deployment didn't report a region. |
| Created date | When the deployment was created. |
If a deployment failed, the error is shown under its name with a see the log link. If there are no deployments yet, the table shows No deployments yet and a second New deployment button. If the panel is narrow, the table scrolls sideways inside its card.
Show or hide removed deployments
Removed (destroyed) deployments are hidden at first. Select Show N removed above the table to list them too, and Hide N removed to fold them away again. The count next to it, for example "3 deployments", is the number of rows the table currently shows.
Search for a deployment
Type in Search deployments. The table filters as you type, matching the deployment ID, run ID, provider, model, status or name, whether you type capitals or not. If nothing matches, you see No matching deployments. Select Clear search to show everything again.
Move between pages
The footer shows "Showing X-Y of N deployments". Choose 5, 10, 25 or 50 rows per page (10 at first), and use the first, previous, page number, next and last buttons to move through the list.
Open a deployment's actions
Select ⋮ at the end of a row. The menu only lists actions that apply to that deployment:
| Action | When it's offered | What it does |
|---|---|---|
| Information | The deployment has a public IP address. | Shows the app's address, the server's IP, who to log in as, a readiness check (Check again re-runs it), DNS records to add, the SSH command, and the files to download. |
| Logs | Always. | Opens the deployment log (next step). |
| Preview | A dry-run plan was saved. | Shows what the plan would create, change and remove. Nothing in it has been created. |
| Server key | A key file was generated when the deployment was set up. | Downloads the SSH key (.pem) for the server. |
| State file | Always. | Downloads the infrastructure state file. |
| Remove | The deployment isn't already destroyed. | Tears the deployment down (see Remove a deployment). |
You can also select a deployment's name in the Deployment ID column to open its information.
Read the deployment log
Select Logs. The Deployment log window opens, titled with the deployment's internal ID (for example dep-20260929095523-9d7dbf). It shows the provisioning output: database migration output, each cloud resource being created or destroyed, and a final summary such as "Destroy complete! Resources: 10 destroyed." While a deployment is still running, the log keeps updating on its own. Select Close when you're done.
Remove a deployment
Choose Remove
Select ⋮ on the deployment's row, then Remove. The Remove … window lists What goes: the server and everything running on it, its data disk and the database on it, its public address and any DNS records Dalfin created, and the images copied into the cloud account's registry. Your own SSH key, and any registry you made yourself, are kept.
Enter the credentials again
Under Credentials, enter the same kind of credentials you used to deploy (for example the DigitalOcean API token). They're sent with this request only and not stored, which is why they're asked for again.
Type destroy and confirm
Under Confirm, type destroy in Type destroy to continue. Remove permanently becomes available once the word and every credential are filled in. Select it to remove the deployment, or Keep it to close the window without changing anything.
Statuses
| Status | Meaning |
|---|---|
| Pending | The deployment is queued and hasn't started yet. |
| Deploying | The cloud resources are being created. The current phase is shown next to the age in the row. |
| Live | The deployment finished. Use Information to check the app is really ready (the server may still be starting up or waiting for its certificate). |
| Planned | A dry run (Preview changes) worked out a plan. Nothing was created. |
| Failed | Something went wrong. Open Logs for the cloud provider's own message. |
| Destroyed | The deployment's cloud resources have been removed. Hidden unless you select Show N removed. |
Remove can't be undone. The server, its data disk and the database on it are deleted from your cloud account. Download anything you need first, for example the State file.
The State file holds the database password and the registry credential in plain text. Treat it as a secret. If a row says the data disk was kept and is no longer tracked, that disk keeps costing money in your cloud account until you delete it there yourself.