MiravoPersistence
Restore structural runtime state across restarts from snapshots under `$MIRAVO_HOME/state/`.
Technical details
Know where snapshots live
Snapshots live under $MIRAVO_HOME/state/. Default base directory: ~/.miravo.
Restore structural state, not every transient value
Miravo persists instances, IDs, browse paths, parameters, operating hours, lifecycle stage, active faults, template run assignments, and enabled adapter config. It does not persist current member values, in-flight protocol traffic, or exact RNG position.
A boot snapshot is written after startup reconciliation and before the first tick. Later writes are debounced and serialized to avoid write races.
Start fresh or clear persisted state
Ignore the saved snapshot on the next boot.
miravo start --reset-stateDelete the saved snapshot and clear the current runtime.
miravo reset --clear-persistenceClear persisted state through the admin API.
curl -s http://127.0.0.1:8080/commands \
-H 'content-type: application/json' \
-d '{"type":"resetSimulation","clearPersistence":true}'The embedded Console does not read snapshot files directly. Live operator state comes from /bootstrap and /ws.
Reference
| Path, flag, or rule | Notes |
|---|---|
MIRAVO_HOME | Base directory for registry and state |
$MIRAVO_HOME/state/<environment>.json | Snapshot path |
miravo start --reset-state | Ignore any saved snapshot on boot |
miravo reset --clear-persistence | Clear the current runtime and remove the saved snapshot |
| Restore precedence | Existing snapshot is authoritative over boot-time structural config |
| Not persisted | Current member values, exact RNG cursor, live subscriptions, in-flight messages |
Related pages
Architecture
Tick-loop boundary.
Custom content
Relocate registry and state.
CLI ⭢ miravo reset
Reset and persistence-clearing commands.
Environments
Restore in practice.
Was this page useful?
Last updated on