Configure a database
Open a database resource and select Configuration to change its engine settings, credentials, networking, storage, health check, and resource limits.
The available pages depend on the database engine and the resource state. For example, Backups is available only for engines supported by Coolify's database backup workflow, while Import Backup is available only for supported restore paths.
Configuration pages
| Configuration page | What it controls | Guide |
|---|---|---|
| General | Database identity, image, credentials, engine settings, network access, and proxy settings. | Review General settings |
| Environment Variables | Runtime variables passed to the database container. | Configure environment variables |
| Servers | The server and destination where the database runs. | Configure multi-server deployments |
| Persistent Storage | Volumes, directories, and files mounted into the database container. | Configure persistent storage |
| Import Backup | Restore a supported PostgreSQL, MySQL, MariaDB, or MongoDB backup. The page is also shown for unsupported engines, where Coolify displays that restore is not supported. | Restore a database |
| Webhooks | Authenticated requests for database operations from external automation. | Deploy webhooks |
| Healthcheck | The Docker health probe used to report database health. | Configure health checks |
| Resource Limits | CPU and memory limits applied to the database container. | Configure resource limits |
| Resource Operations | Clone the database to another destination or move it between projects and environments. | Clone or move a database |
| Metrics | CPU and memory usage for the database container. | Monitor resource metrics |
| Tags | Team-level labels used to organize resources. | Organize resources with tags |
| Danger Zone | Destructive actions, including deleting the database resource. | Delete a database |
Apply configuration changes
Saving a setting updates the database resource configuration. It does not always recreate the running container immediately.
Restart or redeploy the database after changing settings that affect its container, including:
- image, credentials, or engine configuration
- environment variables
- persistent storage mounts
- ports or public proxy settings
- health-check settings
- resource limits
Use the configuration-change indicator and the database status to confirm whether Coolify is waiting for a restart or redeploy.
Take and verify a database backup before changing a production image, data mount, engine configuration, or credential. A configuration change can prevent the database from starting even when the stored data is intact.