GitOps review and sync
Servestead treats committed configuration as deployment input. The stack manager separates editing from deployment so you can inspect the exact files that will become authoritative.
Open the stack manager
Section titled “Open the stack manager”Select a saved profile and press s. The screen reports two independent states:
- Git reports a clean working tree or local changes that need review.
- Remote reports
commit required,push required,sync required,review required, orin sync.
Review and commit changes
Section titled “Review and commit changes”Use this sequence after adding, editing, or deleting a stack:
- Press
vto inspect staged, unstaged, and untracked changes. - Press
gto stage managed changes understacks/. - Press
c, enter a specific message, and commit the staged stack changes. - Press
pwhen the current branch has anoriginand needs a push.
If the repository has no origin, local committed deployment can still be valid. Normal team branch and pull-request rules still apply outside Servestead.
Deploy one stack
Section titled “Deploy one stack”Select an eligible stack and press r. Servestead deploys its committed configuration and records a stack:<name> run. Uncommitted changes or an unpushed branch block the action when the repository requires them.
Reconcile the repository
Section titled “Reconcile the repository”Press y only after the committed repository matches your intent. Synchronization deploys every current stack and removes managed containers, generated overrides, deployment manifests, and Pangolin resources for stacks deleted from Git.
Servestead deploys the exact committed HEAD. An uncommitted observability Compose change blocks platform deployment, while unrelated working-tree changes do not.
Expected result
Section titled “Expected result”The stack manager reports a clean working tree, an understood push state, and in sync after successful reconciliation. Press h from the profile dashboard to inspect the resulting run and redacted task log.