Deleting a project
Deleting a project is two separate decisions, and CloudPilot keeps them separate on purpose.
What always happens#
- The project record is removed from the panel.
- Its deployment history goes with it.
- Its GitHub webhook is removed, best effort.
What only happens if you ask#
Whether the application is torn down on the server is a separate, explicit choice — a checkbox on the delete dialog, and it is off by default.
The reason is that the app is usually still serving traffic. Removing a row from a list should not take production offline as a side effect. Deleting the record can be undone by creating the project again; taking production down cannot.
When you do tick it, CloudPilot removes the project's files and configuration from the server, including the release directories that rollback would have used.
It stops the application and removes its files. There is no rollback afterwards, because the releases rollback would use are part of what is deleted. If you want the site to keep running and only want it out of the panel, leave the box unticked.
Protected projects#
If the project is protected, the deletion waits for approval like any other gated action.
If the server is offline#
The delete still completes. The teardown is attempted but never blocks removing the record — otherwise a server that is offline or half-cleaned would leave the project permanently undeletable, with no way to see why.
This means: deleting a project while its server is offline can leave files on that server. If you needed those gone, check the machine once it is back.
The record of it#
Who asked for the delete is written to the audit log before anything is removed, so that a delete which fails halfway through still has a record of who started it. The two cases — removing the record, and tearing down the app — are logged separately, because only one of them takes something offline.
Raise a ticket and someone will pick it up. Sign in with the same account you use for the panel.
Raise a ticket