Gracefully shut down the nSelf stack. Your database and all data volumes are preserved. Run nself start to bring everything back up.
# Stop all services
nself stop
# Same thing — alias
nself down
# Stop specific services, leave the rest running
nself stop redis mailnself stop [SERVICES...] [FLAGS]nself stop sends a graceful shutdown signal to every running container in the nSelf stack, waits for them to exit cleanly, and removes the containers. Data volumes — Postgres data, MinIO objects, Redis state — are untouched. Run nself start to restore the stack to exactly the state it was in before you stopped.
Pass one or more service names to stop only those services while leaving the rest running. This is useful for restarting a single component without taking down the whole stack.
nself down is an alias for nself stop. Both are identical.
To wipe data volumes along with stopping the stack, use nself reset instead. nself stop never deletes data.
| Argument | Description |
|---|---|
SERVICES | Optional. One or more service names to stop: postgres, hasura, auth, nginx, redis, storage, mail, search, functions, admin, or any plugin name. Omit to stop everything. |
| Flag | Type | Default | Description |
|---|---|---|---|
--timeout | int | 30 | Seconds to wait for containers to exit cleanly before killing them |
--force | bool | false | Kill containers immediately without waiting for a graceful exit |
nself stop
# Stopping nginx... done
# Stopping hasura... done
# Stopping auth... done
# Stopping postgres...done
# All services stopped. Data volumes preserved.nself stop redis
nself startnself stop postgres --timeout 60nself stop hasura --forcenself stop is safe to run at any time. It:
--timeout seconds for Postgres to complete in-flight writesIf you want to wipe data and start clean, use nself reset (requires explicit confirmation).
0 — all specified services stopped cleanly1 — one or more services did not exit within --timeout and were killed2 — invalid service name or arguments