Advanced settings
Open an application, then select Advanced in the application settings sidebar. 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, submodules, Git LFS, and clone depth. Preview controls are on Preview Deployments. |
| Docker Compose application | Compose deployment and 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, and commit metadata.
Build cache
Under Build cache, choose Rebuild from scratch every time to prevent Coolify-generated builds from reusing Docker build cache on every deployment.
Choose Use Docker build cache 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.
Build arguments
Build arguments defaults to Inject build args automatically. Coolify adds ARG instructions for application variables that are available during the build.
Choose Managed manually in Dockerfile when the Dockerfile declares and manages every required ARG itself. This avoids duplicate injected instructions and gives the Dockerfile complete control over cache boundaries.
Source commit availability
Under Source commit availability, choose Available during build when the image build needs SOURCE_COMMIT, the selected Git commit hash.
The default is Runtime only (preserves cache) 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.