Lifecycle
Update Trestle
Treat the executable and data schema as one release operation. Back up first, verify the new artifact and retain the previous binary until the new version is proven.
Checksum-verified updater
curl -fsSL https://trestle.dev/update.sh | sh
curl -fsSL https://trestle.dev/update.sh | sh -s -- --dry-run
curl -fsSL https://trestle.dev/update.sh | sh -s -- --version v0.2.0The updater locates the expected installation, refuses symlinks and ambiguous root usage, verifies the selected archive against the release checksum, retains trestle.previous, and atomically replaces only the executable. It never modifies instance data or configuration.
- Read the release notes and compatibility boundary.
- Create and download a consistent Trestle backup.
- Run the updater dry-run and stop the service.
- Apply the update, start it and inspect logs.
- Check readiness, version, administrator login, records, files, realtime and queued delivery.
curl -fsS https://trestle.example.com/system/ready
./trestle versionDo not run two Trestle processes against one SQLite data directory. Blue-green deployment requires independent restored data, not shared storage.