Files
computer-playbook/docs/administration/deploy.md
kevinveenbirkenbachandClaude Opus 4.8 ea9ebe0de3 refactor(inventory): rename prod inventory to production
Standardize the private inventory dir on the fully spelled "production" (matching inventories/development). Update the role README template (SPOT) and regenerate 153 role READMEs plus the admin deploy guide; add inventories/production/ to .gitignore, propagated to .dockerignore via make fix-dockerignore.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-21 19:08:08 +02:00

45 lines
1.9 KiB
Markdown

# Deploy Guide 🚀
Use this guide to create inventories, run a full deploy, and redeploy an existing environment with `infinito` commands only. The audience is the operator running deploys against a managed (production or staging) host. Contributors iterating on a local development stack should follow [Local Deploy](../contributing/actions/deploy.md) instead.
## Full Deploy 📦
Create or refresh the inventory first, then deploy against the generated inventory file.
### Create or Refresh the Inventory 📝
```bash
infinito administration inventory provision /etc/infinito.nexus/inventories/production \
--inventory-file /etc/infinito.nexus/inventories/production/devices.yml \
--host localhost \
--vars-file inventories/<env>/default.yml \
--include 'web-app-nextcloud,web-app-keycloak'
```
### Run the Deploy 🛠️
```bash
infinito administration deploy dedicated /etc/infinito.nexus/inventories/production/devices.yml \
--password-file /etc/infinito.nexus/inventories/production/.password \
--log /etc/infinito.nexus/logs \
--diff \
-vv
```
## Redeploy 🔁
When you need to redeploy after changes, repeat the same two `infinito` commands:
1. Re-run `infinito administration inventory provision ...` to refresh the inventory file and included app list.
2. Re-run `infinito administration deploy dedicated ...` against the same inventory file.
## Inventory Notes 📒
- Keep one inventory directory per environment.
- Store the password file next to the inventory file.
- Update `--include` whenever the target app set changes.
- Use a `--vars-file` that matches the target environment. Production deploys MUST NOT point at the development sample file.
For CLI installation prerequisites, see the [Installation Guide](installation.md).
For the local development deploy flow (make targets, matrix variants, single-variant pinning), see [Local Deploy](../contributing/actions/deploy.md).