General settings
Open an application, then select Configuration > General. This page contains the settings that determine what Coolify builds or pulls, where it finds source files, which container ports receive traffic, and how the resulting container starts.
The controls change according to the application's source, Build Pack, and deployment destination. A setting that does not apply to the selected method is hidden rather than disabled.
Settings available by deployment method
Use this table to identify which part of General applies to the application:
| Deployment method | Main settings shown |
|---|---|
| Nixpacks or Railpack | Build commands, repository paths, static-site controls, publish directory, domains, registry output, network settings, and container labels. |
| Static | Static server image, repository root, custom Nginx configuration, domains, registry output, network settings, and container labels. |
| Dockerfile from Git | Repository root, Dockerfile path, optional build stage, domains, registry output, network settings, and container labels. |
| Dockerfile without Git | The Dockerfile stored in Coolify, optional build stage, domains, registry output, network settings, and container labels. The Build Pack selector is not shown. |
| Docker Compose from Git | Compose file paths, per-service domains, parsed Compose content, repository preservation, optional Compose commands, and label escaping. |
| Docker Image | Image name, tag or hash, container options, domains, network settings, and container labels. The Build Pack selector is not shown. |
Docker Compose applications do not use the single-container Network, HTTP Basic Authentication, or editable Container Labels controls on this page. Configure ports, health checks, service environment entries, volumes, and labels in the Compose definition.
General contains the application's identity and public domain configuration.
Application details
Name identifies the application throughout the Coolify dashboard. It is required. Description is optional and can record the workload's purpose, owner, or other team context.
Select Details to view the application UUID and other resource information.
Domains
For a non-Compose application, Domains contains the public URLs that Coolify Proxy routes to the container. Separate multiple domains with commas.
https://app.example.com
https://example.com/api
https://example.com:3000
https://example.com:8080/apiA port in the domain tells Coolify Proxy which port to use inside the container. It does not expose that port directly on the deployment server. For example, https://example.com:3000 is opened by visitors as https://example.com, while the proxy forwards the request to port 3000 in the container.
For Docker Compose, Coolify shows a separate Domains for <service> field for each parsed non-database service. Add the internal port to the domain when that service does not listen on port 80.
Generate Domain creates a domain from the wildcard domain configured for the deployment server.
Redirect www traffic
Direction controls how Coolify handles www and non-www versions of a domain:
- Allow www & non-www. serves both versions.
- Redirect to www. redirects the non-
wwwversion towww. - Redirect to non-www. redirects the
wwwversion to the root domain.
Add both domain forms under Domains and create their DNS records before selecting a redirect direction.
The Domains and Direction controls become read-only when manual container-label editing is enabled. In that mode, the proxy labels become the source of routing behavior.
Read Domains before changing production routing.