0.4.0 lets you deploy Compose stacks from FleetOps, to the local host or to any host behind an agent. Update the image tag and restart; the database migrates on start.
Write a stack in the browser
Open Stacks in a Docker environment and choose New stack. Write the Compose file and its variables next to it. Variables are sealed with the server key, and their values stay masked for anyone without the permission to reveal them. FleetOps runs Compose itself, so the host needs no docker compose binary.
See the plan before you deploy
Every deploy starts with a review. FleetOps lists each service it will create, recreate or remove, names the fields that changed for each one it recreates, and shows a diff of the file against the last deploy. Nothing touches the host until you confirm, and the plan you confirmed is the plan that runs: if the stack changed in the meantime, FleetOps asks you to review again.
A failed deploy puts the stack back
Replaced containers are stopped and kept aside until every service is up, and only then removed. If a container fails to start, FleetOps restores the stack as it was. The same happens after a server restart or a lost agent cuts a deploy off: FleetOps finds the half-finished deploy and undoes it.
Revisions and rollback
Every deploy is a revision. Pick any earlier one, review its plan the same way, and roll back. Deploying and removing stacks needs the Operator role on the environment, and each deploy is in the audit log.
Limits
build, secrets and configs are not supported yet. Projects started outside FleetOps with docker compose are still listed, with start, stop, restart and down.
Next
Git-backed stacks are merged for the next release: a stack takes its Compose file from a branch of a git repository and syncs on a push webhook or by polling. After that, port-forward, and API tokens for Enterprise. See the roadmap.