This commit updates multiple roles to ensure compatibility with Ansible 2.20. Several include paths and task-loading mechanisms required adjustments, as Ansible 2.20 applies stricter evaluation rules for complex Jinja expressions and no longer resolves certain relative include paths the way Ansible 2.18 did. Key changes: - Replaced legacy once_finalize.yml and once_flag.yml with the new structure under tasks/utils/once/finalize.yml and tasks/utils/once/flag.yml. - Updated all include_tasks statements to use 'path_join' with playbook_dir, ensuring deterministic and absolute file resolution across roles. - Fixed all network helper includes by converting direct relative paths such as 'roles/docker-compose/tasks/utils/network.yml' to proper Jinja-evaluated paths. - Normalized MATOMO_* variable names for consistency with the updated variable scope behavior in Ansible 2.20. - Removed deprecated patterns that were implicitly supported in Ansible 2.18 but break under the more strict variable and path resolution model in 2.20. These changes are part of the full migration step required to ensure the infinito-nexus roles remain stable, deterministic, and forward-compatible with Ansible 2.20. Details of the discussion and reasoning can be found in this conversation: https://chatgpt.com/share/69300a8d-24d4-800f-bec0-e895a695618a
Docker Compose
Description
This Ansible role manages Docker Compose project structures and workflows for applications on Arch Linux. It creates dedicated instance directories, manages .env and docker-compose.yml files, and provides automation logic for project reset, rebuild, and startup sequences.
Refer to the Docker Compose documentation, the Arch Wiki – Docker, and Compose CLI reference for more details.
Overview
This role creates a flexible directory layout for managing Docker Compose projects across environments. It ensures directories are initialized, optionally reset, and kept clean using internal flags like MODE_RESET or MODE_CLEANUP.
Purpose
To offer a centralized, extensible system for managing containerized applications using Docker Compose within the Infinito.Nexus architecture. The role allows easy integration of services, secrets, configurations, and custom behaviors per application.
Features
- Dynamic Directory Structure: Creates per-application instance folders for Compose setups.
- Reset Logic: Cleans previous Compose project files and data when
MODE_RESETis enabled. - Handlers for Runtime Control: Automatically builds, sets up, or restarts containers based on handlers.
- Template-ready Service Files: Predefined service base and health check templates.
- Integration Support: Compatible with
sys-svc-proxyand other Infinito.Nexus service roles.
Administration Tips
For administration tips checkout this.
Credits 📝
Developed and maintained by Kevin Veen-Birkenbach
Learn more at www.veen.world
Part of the Infinito.Nexus Project
License: Infinito.Nexus NonCommercial License