How do I update GoModel?
Back up your database first — Updating GoModel has the backup commands for each storage backend, plus verification and rollback. Then:- macOS / Linux
- Windows
- Docker
Re-run the installer — it always fetches the latest release and replaces
the binary in place:
How do I check which version I’m running?
Can I install a specific version, or roll back?
Yes — setGOMODEL_VERSION before running the installer:
$env:GOMODEL_VERSION first. With Docker, use a version tag
(enterpilot/gomodel:X.Y.Z) instead of latest. Replace X.Y.Z with a
published GoModel release.
Is updating safe for my data?
Yes, updating is. The schema is migrated on startup, and an update never moves or deletes your database, configuration, or cache. Rolling back needs care. Most migrations are additive, and an older binary ignores what it does not know about — but some releases rebuild storage into a new shape, as scoped budgets and rate limits did, and the older binary will not find what it expects. Restore a backup taken before the update instead. GoModel ships fast, so take one every update: Updating GoModel has the commands.Where does GoModel store its data?
When a./data directory exists next to where you launch GoModel (existing
deployments, the Docker image), the database stays at ./data/gomodel.db.
Otherwise the binary uses your OS’s conventional per-user directories:
The resolved database path is printed at startup (
storage configured).
SQLITE_PATH overrides the database path, and GOMODEL_CACHE_DIR overrides the
model cache directory. Available from
v0.1.54; older binaries always use ./data relative to the working
directory.
How do I uninstall?
Remove the binary and, if you want a clean slate, the data directories:%LOCALAPPDATA%\Programs\gomodel (and
%LOCALAPPDATA%\gomodel for data), then remove the folder from your user
PATH. For Docker, remove the container and image as usual.