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 instead.
Full Deploy π¦ΒΆ
Create or refresh the inventory first, then deploy against the generated inventory file.
Create or Refresh the Inventory πΒΆ
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 π οΈΒΆ
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:
Re-run
infinito administration inventory provision ...to refresh the inventory file and included app list.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
--includewhenever the target app set changes.Use a
--vars-filethat matches the target environment. Production deploys MUST NOT point at the development sample file.
For CLI installation prerequisites, see the Installation Guide. For the local development deploy flow (make targets, matrix variants, single-variant pinning), see Local Deploy.