coollabsio / coollabsio/coolify-cli
[Feature Request] Add 'database restore' command to CLI to enable full Disaster Recovery automation
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 467
- Forks
- 69
- PR merge metrics
- No merged PRs in 30d
Description
Currently, the coolify-cli allows users to list and trigger database backups (e.g., coolify database backup trigger), which is excellent for automation. However, there is no equivalent command to restore these backups via the CLI.
To perform a restore programmatically today, users must rely on complex workarounds involving direct Docker container manipulation (e.g., docker cp, docker exec) or manual interaction via the web UI. This limitation prevents the creation of fully automated Disaster Recovery scripts or "Clone to Staging" pipelines where a database needs to be refreshed from a backup without human intervention.
I would like to see a new command added to the CLI that handles the restore process, mirroring the existing backup functionality.
Proposed Syntax:
Restore a specific backup to a target database
coolify database restore --id <database_uuid> --backup <backup_uuid_or_filename>
Desired Behavior:
- The CLI accepts the target database UUID.
- The CLI accepts the specific backup ID (from the list obtained via coolify database backup executions).
- If the backup is stored in S3/MinIO, the CLI handles the download automatically.
- The CLI injects the dump into the database container, effectively performing the restore.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the existing coolify database backup trigger command and the database backup executions used to obtain backup IDs. Define how the proposed coolify database restore --id ... --backup ... flow should handle local and S3/MinIO backups, then verify that it restores the selected backup into the target database and supports disaster-recovery automation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cli, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100