Documentation
Yardmaster runs Ansible, Bash, Terraform, and Python across a fleet and treats every run as
structured data. One binary: serve is the API, the executor, the scheduler, and the web UI;
worker adds capacity.
State lives in one database, SQLite by default or PostgreSQL by DSN. These pages also render inside
the app at /ui/docs.
| Guide | What |
|---|---|
| Quickstart | Zero to a first run in a few minutes. |
| Switching from AWX | Import what you have, or set up from scratch. |
| Tutorials | Task-focused walk-throughs for AWX and Semaphore users. |
| Concepts | Runs, splits, pipelines, projects, templates, and the rest. |
| Configuration | Every command, flag, and environment variable. |
| Features | The full capability list. |
| HTTP API | Every endpoint the server exposes. |
| Migration | Moving off AWX or Semaphore in detail. |
| Comparison | How Yardmaster compares to AWX and Semaphore. |
For deployment, the repository root holds a docker-compose.yml for a server, a database, and a
worker, and deploy/helm holds a Helm chart.