restart
Restart services with zero downtime.Options
| Short | Long | Description |
|---|---|---|
-c | --config | Path to the configuration file. When specified, reloads the configuration and restarts all services with the new settings |
-s | --service | Name of a specific service to restart. If not specified, all services are restarted |
-p | --project | Target a stable project id when restarting services |
- | --daemonize | Start the supervisor before restarting if it is not already running |
- | --sys | Opt into privileged system mode. Requires running as root |
- | --drop-privileges | Drop child service privileges during spawn. In root/system mode, services without an explicit user run as nobody |
- | --log-level | Set logging verbosity for this invocation. Accepts named levels (trace, debug, info, warn, error, off) or numeric values (5-0) |
Examples
Restart all services
Restart specific service
Restart with new configuration
Restart a project and reload its stored manifest
--config is omitted, restart --project reuses the config path the
running supervisor already recorded for that project and reloads it from disk.
Manifest changes are applied: services added since the last load start, services
removed from the manifest stop, and changed commands take effect. You do not
need to pass --config again if the project already has a known config path.
Cron units
restart --service <CRON_UNIT> is invalid. Cron units are scheduler entries,
not persistent services, so they cannot be restarted directly:
Deployment strategies
Services configured withdeployment.strategy: rolling get zero-downtime restarts:
- New instance starts
- Health checks pass
- (Optional) blue/green
switch_commandshifts traffic to candidate slot - Old instance receives
SIGTERM - Grace period allows requests to complete
- Old instance stops
See also
start- Launch servicesstop- Stop services- Deployment strategies