Operations and upgrades#
Syndicate state, event data, configuration, worktrees and terminal sessions are separate operational assets.
Before you start#
- Record the installed version and service status.
- Stop or preserve active writable sessions.
- Ensure useful worktree commits are reachable from a branch or remote.
- Back up the Syndicate state directory and configuration.
Use syndicate status, syndicate doctor and the service logs before and after
an upgrade. Install an immutable release version, restart the Host and
terminal-host services, then generate a new dashboard invitation.
Do not delete quarantined or leased worktrees merely to make a status check green. Investigate the provider process and preserve evidence first.
Verify#
syndicate version
syndicate doctor
syndicate host status
syndicate workstation list --json
git -C /srv/code/project worktree listConfirm the new version, healthy services, expected workstations and unchanged repository state. Test one read-only session before resuming writes.
If it does not work#
| Symptom | Check | Recovery |
|---|---|---|
| A service will not restart after an upgrade | The user services, then syndicate doctor |
See Start with doctor |
| A worktree is left behind after rollback | Whether a session still holds it | See A worktree cannot be released |
| A backup restores but sessions are missing | Whether state outside the prefix was captured | Repositories, worktrees and the state directory sit outside the install prefix |
| Rollback leaves the dashboard unreachable | The dashboard origin after the version change | See Browser access |