0.5.0 connects stacks to git. Update the image tag and restart; the database migrates on start.
A stack from a git repository
Choose New stack, then From a git repository. Give the HTTPS URL, the branch and the path of the Compose file in it (compose.yaml unless you say otherwise), and an access token if the repository is private. The token is sealed with the server key like other secrets. Variables stay in FleetOps, sealed, so the repository never holds them.
Sync on push or by polling
A git stack syncs three ways: Sync now on its Git tab, polling on an interval of a minute or more, or a push webhook from GitHub, GitLab, Gitea or Forgejo. The Git tab shows the webhook URL and its secret to paste into the provider; FleetOps checks the secret on every call, and limits how often each address can call it.
Deploy each version, or review it
With auto-deploy on, each new commit is planned and deployed the same way a deploy from the browser is, and a failed one puts the stack back as it was. A source that deploys itself both writes and ships the stack, so turning auto-deploy on needs permission to deploy, not only to edit. With it off, a new commit shows as Update available: open it, review the plan and the diff, and deploy when you are ready.
Rolling a git stack back to an earlier revision pauses its sync, so the next push doesn’t undo the rollback. Choose Resume to follow the branch again.
Limits
SSH URLs, submodules and Git LFS are not supported. FleetOps fetches only the branch head, one commit deep, and reads only the Compose file.
Next
Port-forward, then API tokens, SIEM forwarding and long audit retention for Enterprise. See the roadmap.