CremindUpgrading
Moving an existing Cremind install to a newer release with the cremind upgrade CLI or the in-app updater.
Cremind upgrades in place. Re-running the installer keeps your existing config and database, and the built-in cremind upgrade command (with a matching in-app updater) takes a backup, installs the new package, runs migrations, and restarts — rolling back if any step fails. The common one-liner is cremind upgrade -y, and cremind upgrade check reports whether a newer release is available without changing anything.
Documentation in progress
This page is being written. In the meantime, the upgrade flow is implemented in the app/upgrade module and the cremind upgrade CLI command, and exposed to the UI through the upgrade API. You can also re-run the installer to upgrade in place, or see Files written for what's preserved across upgrades.
Files Written
Exactly what each install mode creates on disk under ~/.cremind, plus the environment-variable overrides for staging and offline installs.
First-Run Setup Wizard
Walk through the browser-based wizard that bootstraps a fresh Cremind server — LLM provider, deployment choices, per-service storage, and the first admin profile.