Configure an application
Open an application and select Configuration to change how Coolify prepares its images, starts its containers, exposes traffic, and operates the workload.
The available pages depend on the application type and destination. For example, Git Source appears only for Git-based applications, Swarm appears only for a Docker Swarm destination, and the application Healthcheck page is not used for Docker Compose.
Configuration pages
| Configuration page | What it controls | Guide |
|---|---|---|
| General | Application identity, build method, domains, image settings, ports, container labels, and deployment commands. | Review General settings |
| Advanced | Build cache, container naming, automatic and preview deployments, Git clone options, proxy behavior, restart limits, log drains, and GPU access. | Review Advanced settings |
| Swarm | Docker Swarm service settings for applications deployed to a Swarm destination. | Configure Docker Swarm |
| Environment Variables | Build-time and runtime values passed to the application. | Configure environment variables |
| Persistent Storage | Volume, directory, and file mounts attached outside the replaceable container filesystem. | Configure application persistent storage |
| Git Source | The connected Git source or deploy key for a Git-based application. | Configure a source |
| Servers | The servers selected to run the application. | Configure multi-server deployments |
| Scheduled Tasks | Commands that Coolify runs inside the application container on a schedule. | Configure application scheduled tasks |
| Webhooks | Authenticated deployment webhooks and manual Git-provider webhooks. | Use deploy webhooks Configure manual Git webhooks |
| Preview Deployments | Pull-request or merge-request environments and manual preview deployments. | Configure preview deployments |
| Healthcheck | HTTP or command checks used to determine whether a non-Compose application is healthy. | Configure health checks |
| Rollback | Previously built images that are still available for deployment. | Roll back an application |
| Resource Limits | CPU and memory limits applied to the application containers. | Configure resource limits |
| Resource Operations | Clone the application to another destination or move it between projects and environments. | Clone or move an application |
| Metrics | Container metrics collection and display. | Monitor resource metrics |
| Tags | Team-level labels used to organize resources. | Organize resources with tags |
| Danger Zone | Destructive actions, including deleting the application. | Delete an application |
Apply configuration changes
Saving a setting updates the stored configuration. It does not necessarily replace the running container immediately.
Deploy or restart the application after changing settings that affect its container, including environment variables, storage, health checks, ports, networks, and resource limits. Build configuration changes require a deployment that creates or reuses an image.
Use:
- Deploy for the first deployment
- Redeploy to run the deployment flow again
- Restart to recreate the runtime through the deployment queue; source-based paths reuse an existing image when eligible, while Docker Image pulls the saved image reference again
- Force deploy (without cache) to disable cache for a Coolify-generated source build; custom Docker Compose build commands control their own cache flags
Read Build and deployment model for the difference between image preparation and container replacement.