Application configuration

Application settings describe the next container Serversinc should create. They do not change a container that is already running.

Apply a configuration change

1. Open the application and choose the tab for the setting you need to change.
2. Save the new value.
3. Review the pending-changes banner.
4. Select Deploy to create a replacement container with the new configuration.
5. Follow the deployment until it completes.

Some settings, such as the deploy strategy and CPU and memory limits, don’t show in the pending-changes banner but still need a deployment. See Application settings.

Configure the runtime

The application page separates configuration by concern:

• Variables for environment variables and secret values.
• Volumes for bind mounts and named Docker volumes.
• Networks for Docker network membership.
• Ports for publishing container ports on the host.
• Labels for container metadata and advanced routing configuration.
• Settings for source, deployment strategy, health checks, stop grace, CPU, memory, and registry credentials.

Environment variables and secrets

Mark passwords, tokens, and private keys as secrets.

You can paste a .env file to add several variables at once. Check the duplicate keys and overwrite choices before you save.

Storage and networks

Volumes can be bind mounts or named Docker volumes, mounted read-write or read-only.

Attach an application only to networks that exist on its assigned server. Port mappings publish container ports directly on the host. For web traffic, use a domain routed through the managed reverse proxy instead.

Caution

Changing or removing a mount can make existing data disappear from the replacement container even though the data still exists on the host or volume. Check the source and target paths before deploying.