General settings
Open an application, then select General in the application settings sidebar. 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 strategy, 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 strategy 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 strategy selector is not shown. |
Docker Compose applications do not use the single-container Network, HTTP Basic Authentication, or editable Active 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 an Access summary linking to its 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.
Use the resource menu in the top bar to navigate between applications in the active environment.
Domains
Select Domains in the application settings sidebar, or use the domain-management action in Access. Add and edit individual domains there rather than entering a comma-separated list on General.
Choose Add domain, then enter Protocol, Domain, optional internal Port, and optional Path. For Docker Compose applications, also choose the receiving Service.
A domain port selects a port inside the container; it does not publish that port on the server. For example, HTTPS with domain example.com and port 3000 serves visitors at https://example.com while forwarding to container port 3000.
Edit a domain to set www redirect and Search engine indexing. The Domains page also provides Redirect HTTP to HTTPS when an HTTPS domain is configured.
When labels are managed manually, configure routing in the labels instead. Read Domains before changing production routing.