This PR enables database detection and backup scheduling for Docker Compose deployments via GitHub App (using the dockercompose buildpack).
When deploying a Docker Compose file via GitHub App, database services are not detected and ServiceDatabase records are not created. This means automated backups are not available for databases in these deployments.
| Deployment Method | Model | Creates ServiceDatabase | Backups Available |
|---|---|---|---|
| Empty Docker Compose | Service |
✅ Yes | ✅ Yes |
| GitHub App (dockercompose buildpack) | Application |
❌ No | ❌ No |
| One-click Services (e.g., Supabase) | Service |
✅ Yes | ✅ Yes |
Added support for creating ServiceDatabase records when parsing Docker Compose files for Application models (GitHub App deployments).
application_id column to service_databases tableservice_id nullable to support both relationship typesapplication() relationshipisApplicationDatabase(), isServiceDatabase(), getServer(), getParentResource()serviceDatabases() relationshiphasServiceDatabases() and getBackupableDatabases() helper methodscoolify.service.subType=database label support for manual overrideServiceDatabase creation logic for Application model pathDatabaseBackups Livewire component for backup managementUsers can manually specify that a service is a database by adding:
services:
my-custom-db:
image: my-company/custom-db
labels:
- coolify.service.subType=database
Added comprehensive test suite:
Will add demo video before merge
Fixes #7528
/claim #7528
Erdogan Kervanli
@erdogan98
Ilias Ism
@me