Repository navigation
Release v5.3.0
The sandbox container can now use a Chronicle kernel that is already running, so a development session keeps its event log in a database across restarts.
Added
- Set
CRATIS_CHRONICLE_CONNECTION_STRING_FILEto a mounted file holding a Chronicle connection string and the sandbox entrypoint starts no kernel of its own and does not wait for port 35000. Input validation,--warmand the warm handoff restart are unchanged (#1040) - The entrypoint prints the connection with the password masked, and an unreadable or empty file exits with code 78 before anything starts
- A "Use an external Chronicle kernel" section in the Stage container documentation