0.6.0 fills in the parts of Compose that stacks left out, and lets a git stack fetch over SSH. Update the image tag and restart; the database migrates on start.
Builds
build works. A git stack builds its images from the repository: only the code under a service’s build context is sent, after .dockerignore. Any stack can use dockerfile_inline. Images are built on the target host before any container changes, and the deploy review shows what will be built. Each image is tagged from its context’s git tree, so a commit that changes only code redeploys just the services that build it. A rollback uses the images that revision built.
Secrets and configs
secrets and configs work. Put values in the stack’s Secrets tab, or take them from a stack variable or inline content. They are stored encrypted and copied into each container before it starts, so nothing is needed on the host. A secret is never shown again once saved, not even in the container’s Files tab. On a git stack, a config’s file is read from the repository at the same commit as the Compose file.
Git over SSH
A git stack can use an SSH URL, git@host:repo.git or ssh://…, with a deploy key that FleetOps generates for the stack or one you paste. SSH runs inside FleetOps, so the image needs no ssh program. Host keys are checked: GitHub, GitLab and Bitbucket against their published keys, other hosts trusted on the first sync. A changed key stops syncs until someone accepts it in the Git tab.
Limits
Submodules, Git LFS, and passphrase-protected or RSA SSH keys are not supported.
Next
Port-forward, then API tokens, SIEM forwarding and long audit retention for Enterprise. See the roadmap.