Files and directories
For: Operators locating configuration and state.
Locate persistent state by its owner: server, operator or node. Paths below use the default data directories.
Server
| Path | What |
|---|---|
~/.local/share/orchestrator-zero | The default data directory (--data-dir) |
<data-dir>/master.key | The master key, unless --master-key-file points elsewhere: plain base64, or a document wrapped by a key command (master.key.plain, .prev and .wrapped are what the wrap and unwrap-to-file commands keep next to it). Back it up. |
In dev mode with --data-dir, the directory also holds oz0.db (the management database), temporal.db (the embedded Temporal's), operator/ (the operator's credentials and context.json), join-token (a reusable token for dev nodes) and admin-password. Without --data-dir, dev mode uses a temporary directory removed at exit. server backup --dev copies both databases while the server runs; see backups.
Operator
server init writes the first operator's credentials to --operator-dir, by default ~/.config/orchestrator-zero/<cluster>/. server operator issue writes new ones the same way, and operator renew replaces the certificate and key at the same paths, once it has checked them (a renewal stopped halfway leaves operator.key.next or operator.crt.next beside them, and the next command finishes it; operator.key.lock is the lock a command holds while it writes or moves them, so two commands that run at once never act on a pair the other is still writing):
| File | What |
|---|---|
context.json | The cluster's name, the edge and management addresses, the namespace, and the paths below |
ca.crt | The cluster's CA certificate |
operator.crt, operator.key | The operator's certificate and private key. Keep them private. |
Point the CLI at it with export OZ0_CONTEXT=.../context.json or --context. Without either, the CLI looks for ~/.config/orchestrator-zero/context.json.
Node
| Path | What |
|---|---|
~/.local/share/orchestrator-zero-node | The default data directory (--data-dir): the node's identity and key, uv, Python, Node.js, runtimes and state |
<data-dir>/node.json | The node's state, including the list of edges it can fail over to |
<data-dir>/plugins/<name>/<commit>/ | Each installed plugin, with its environments |
Nothing on a node needs a backup: its plugins come from the edge, and a lost node can join again.
Temporary session files
Runtimes record the temporary folders they create so a later start can clean up after a crash. Older runtimes that created no record can leave folders under oz0-sessions, and oz0-t-* or oz0-files-* folders, containing job data. Remove those abandoned folders manually only while no session runs on the node.
A remote session's folder is kept across segments because a later segment may resume it. Cleanup removes a folder unused for a week at runtime startup or when the next remote session starts. A continuously running node with no new remote session can keep it longer.