Skip to main content

​
How do I update GoModel?

Re-run the installer — it always fetches the latest release and replaces the binary in place:
Restart the gateway after updating; there is no in-place hot upgrade.

​
How do I check which version I’m running?

The version is also printed on the first line of the startup log.

​
Can I install a specific version, or roll back?

Yes — set GOMODEL_VERSION before running the installer:
On Windows set $env:GOMODEL_VERSION first. With Docker, use a version tag (enterpilot/gomodel:0.1.53) instead of latest.

​
Is updating safe for my data?

Yes. The database schema is migrated additively on startup, and updates never move or delete your database, configuration, or cache. Rolling back a version is equally safe for typical minor upgrades, though a database written by a much newer version may contain tables an older binary simply ignores.

​
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), and GOMODEL_SQLITE_PATH / GOMODEL_CACHE_DIR override it. 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:
On Windows, delete %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.