CortexDB 0.12.2 — built-in backup, credentials that survive restarts, and a readiness answer that says what works

0.12.2 is 0.12.1 plus fixes from pilot reviews. The data format, the license and the routes are 0.12.1's; the new fields are additions, and upgrading from 0.12.1 is a drop-in replacement.

Getting 0.12.2. From https://customer.cortexdb.ai, Releases. Run the install commands there as they are; they carry your company's license.

Summary

• Backup and restore are in the binary. cortexdb backup DATA_DIR ARCHIVE, cortexdb restore ARCHIVE NEW_DIR and cortexdb backup-verify ARCHIVE take a cold backup of a stopped server: the memories and their indexes, the license, the token minter's keys, the generated API key and the console's settings. Every file is recorded with its SHA-256, and a restore writes nothing until every byte verifies. With Docker, run them with --entrypoint cortexdb on the image (PRODUCTION_DEPLOYMENT.md, "Backup and restore"). Exit codes: 0 done, 2 refused, 3 the server is still running, 4 the archive is damaged.
• Credentials survive restarts. Without CORTEX_V1_MINTER_KEY_DIR, the token minter's keys are now kept in <data dir>/minter-keys/ instead of being made fresh at each start, so a token issued before a restart keeps working, and the keys travel with a backup. A key directory that doesn't load stops the start (MINTER_KEYS_UNUSABLE, exit 78) instead of minting with a new key.
• Readiness says what is proven. GET /v1/admin/ready keeps its status code (storage) and now answers setup (installed, licensed, provider, application, summary) and provider_failing. ?deep=1 makes one real embedding call first, so a new install can prove its provider before the first write.
• Write status tells you whether to re-send. The write-status answer reads the stored write (the same answer before and after a restart) and carries resend: no, new_key, if_sent_within_24h or check_first.
• License renewal reports whether the server works. The renewal request adds checks (provider, application: booleans, each sent only once proven), so our staff can see a pilot's server is working without asking. Nothing about your data is sent (TELEMETRY.md).

Upgrading from 0.12.1

Replace the image or binary and start it on the same data. The first start writes <data dir>/minter-keys/; tokens minted by 0.12.1 used a key that was never stored, so clients holding one get a new token once (as they would after any 0.12.1 restart).

Reference