Configure a Service

Open a Service and select Configuration to change the stack, its Compose components, environment values, storage, automation, and organization.

A Service has two configuration levels:

  • stack settings apply to the complete Docker Compose resource
  • component settings apply to one detected application or database container

Stack configuration pages

Configuration pageWhat it controlsGuide
GeneralService name, description, predefined network access, service-specific fields, Compose definition, and component list.Review General settings
NetworkingCommunication inside the stack, through the coolify network, across servers, and through domains or published ports.Configure Service networking
Environment VariablesValues used when Coolify renders the Service .env file and Compose definition.Configure environment variables
Persistent StoragesParsed volumes, directories, and files grouped by component.Review persistent storage
Scheduled TasksCommands that Coolify runs inside one Service container on a schedule.Configure scheduled tasks
WebhooksAuthenticated requests for Service lifecycle operations.Use deploy webhooks
Resource OperationsClone the Service to another destination or move it between projects and environments.Clone or move a Service
TagsTeam-level labels used to organize and automate resources.Organize resources with tags
Danger ZonePermanent Service deletion and optional Docker cleanup actions.Delete a Service

Component settings

Select Settings on a component card under Configuration > General.

Application component settings can include:

  • display name, description, image, and domains
  • gzip compression and path-prefix stripping
  • aggregate-status exclusion and log drain

Database component settings can include:

  • display name, description, and image
  • public TCP proxy and public port
  • aggregate-status exclusion and log drain
  • supported backups and import controls

Coolify detects common database images while parsing Compose. If a component is classified incorrectly, its settings provide Convert to Application or Convert to Database. Conversion changes how Coolify presents and operates that component; it does not change the image into another database or application.

Apply configuration changes

Saving a setting updates Coolify's stored configuration. It does not always recreate the running containers immediately.

Use:

  • Deploy for the first deployment or a stopped Service
  • Restart to recreate the stack without first pulling newer images
  • Pull Latest Images & Restart to pull the saved image tags and recreate the stack

Review the configuration-change indicator after saving. Verify every component after a restart, especially after changing Compose, images, variables, domains, networks, or mounts.

Back up state before changing the stack

An image, volume, credential, or Compose change can make a stateful component unavailable or incompatible with its existing data. Create a verified backup and read the component's upgrade instructions before changing a production Service.

Continue with configuration guides

On this page