App playbooks
Examples by app shape. Each one shows the before/after diff for the input and explains every line.
For each playbook, the Reference section has a full skill file with the actual YAML. This page is an index — pick the playbook that matches your app and follow the link.
By app type
| Shape | Playbook |
|---|---|
| nginx serving static HTML or an SPA | playbook-nginx-static |
| Node.js with hot reload (Vite, Next.js, nodemon) | playbook-nodejs-dev |
| Generic web app + Postgres | playbook-postgres-app |
| Python web (FastAPI / Django / Flask) | playbook-python-app |
| Rails (web + db + redis + jobs + websocket) | playbook-rails-app |
| Wiki.js | playbook-wikijs |
| WordPress + MariaDB / MySQL | playbook-wordpress |
| Multi-service with shared config | playbook-multi-service |
| Scheduled cron job | playbook-cron-scheduled |
| Test runner on every push or PR | playbook-test-runner |
How to use a playbook
- Find the closest match to what you're trying to launch.
- Read the before/after diff to see what changed.
- Adapt the variable names to your app — most playbooks ask for a subdomain, image tag, DB password, etc.
- Cross-check the relevant recipes at the end of each playbook for any extra patterns you need.
- Run a preview launch before publishing.
If none of the playbooks match exactly, find the closest one and combine it with recipes for the differences. Most real-world templates are 80% one playbook + 20% recipes.
Related
- Recipes — smaller patterns to combine.
- Compose → Fibe — the master conversion flow.
- Before you publish — the polish checklist.