Source Type
Each service is deployed from one of two sources:
For GitHub sources, you can specify the branch, root directory, and whether to auto-deploy on push. See GitHub Integration for details.
Environment Variables & Secrets
Secrets are encrypted at rest and injected into containers at runtime. They are never baked into images. Each secret has a key and an encrypted value, scoped to a single service. You can add, update, and remove secrets from the service settings in the web UI. Secrets are passed as environment variables to the container when it starts.Start Command
Override the container’s default entrypoint by setting a custom start command. This is useful when deploying from pre-built images that need different startup behavior.Resource Limits
You can set CPU and memory limits per service:
New services default to the Large preset: 2 CPU cores and 1024 MB memory. You can change the preset or choose No limit to let the container use whatever resources are available on the host.
Resource limits are runtime caps, not reserved capacity. Placement uses current server health and replica distribution, but it does not require the sum of configured limits to fit as guaranteed minimum allocation.
Health Checks
Health checks verify that a container is ready to receive traffic. When configured, the platform waits for the health check to pass before routing traffic to a new deployment.
Health check statuses:
If no health check command is set, deployment readiness only confirms that the container started. The platform still waits for DNS, proxy routes, certificates, and a successful Traefik configuration reload before marking the rollout complete, but it does not verify that the application inside the container accepts requests. Configure a health check when application readiness matters.