Advanced settings
Open an application, then select Configuration > Advanced. These controls change build caching, deployment triggers, container names, proxy behavior, restart handling, logging, and GPU access.
The available controls depend on the application's source and build method. A setting that does not apply is hidden.
Settings available by application type
| Application type | Additional settings shown |
|---|---|
| Git-based application | Automatic deployments, preview deployments, pull-request access, submodules, Git LFS, and shallow cloning. |
| Docker Compose application | Raw Compose Deployment and Connect To Predefined Network. GPU controls are hidden. |
| Non-Compose application | GPU controls. |
| Every application | Build, container name, proxy, shutdown, restart, and log-drain controls. |
Build controls cache reuse, Docker build arguments, commit metadata, and Docker Compose processing.
Disable Build Cache
Enable Disable Build Cache to prevent Coolify-generated builds from reusing Docker build cache on every deployment.
Leave it disabled for normal deployments. Select Force deploy (without cache) instead when only the next deployment needs a clean generated build.
A custom Docker Compose build command controls its own cache flags, so this setting cannot add or remove cache arguments from that command.
Inject Build Args to Dockerfile
Inject Build Args to Dockerfile is enabled by default. Coolify adds ARG instructions for application variables that are available during the build.
Disable it when the Dockerfile declares and manages every required ARG itself. This avoids duplicate injected instructions and gives the Dockerfile complete control over cache boundaries.
Include Source Commit in Build
Enable Include Source Commit in Build when the image build needs SOURCE_COMMIT, the selected Git commit hash.
The setting is disabled by default so commits with otherwise identical inputs can reuse cached image layers. SOURCE_COMMIT remains available to the running container when it is excluded from the build.
Read Build cache before enabling it for every deployment.
Raw Compose Deployment
This setting appears only for Docker Compose applications. Coolify normally parses the Compose definition and adds the networking, labels, and other configuration it needs to manage the deployment.
With Raw Compose Deployment enabled, Coolify deploys the Compose definition as written. The definition must provide its own proxy labels, networking, and other required runtime configuration.
Read Raw Compose deployment before enabling it.
Connect To Predefined Network
This setting appears only for Docker Compose applications. Enable Connect To Predefined Network when services in the Compose application must communicate with resources attached to the selected Coolify destination network.
Docker Compose services already receive a private network for communication within their own definition. Joining the predefined network is only needed for communication across Coolify resources, and service DNS names can change after joining it.
Read Compose networking before configuring another resource's hostname.