Tree · DeployFlow

What an application looks like in the repository

Adding an application touches two places and nothing else: one entry in app.yaml, and one directory under apps/. Every box below carries the file that holds it.

What an application looks like in the repository Tree diagram of a DeployFlow application: one manifest entry in app.yaml, an application role under apps/name that contains its own checks, and a target file that decides where the application runs. One application app.yaml + apps/<name>/ The manifest app.yaml The role apps/<name>/tasks/main.yml The target src/appctl/targets/ The checks apps/<name>/tasks/main.yml the checks live in the role's own file LEGEND A part of the application The part most tools skip common/ and src/appctl/ name no application — adding one never edits the framework.

THE HEADLINE

Two files, one target

One entry in app.yaml and one directory under apps/. Nothing in common/ or src/appctl/ changes, because the framework never names an application.

The checks are the contract

  • They live in the role's own tasks/main.yml
  • They run after every install
  • Only the application knows what "working" means

One target ships today

proxmox_lxc is implemented. docker_vm and vm are named so a manifest can ask for them and get a clear answer instead of a failure.

what an application looks like · tree deployflow · diagram design