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
Backup Docker to Local
Description
This Ansible role automates the process of backing up Docker volumes to a local folder. It pulls the backup-docker-to-local, installs required software, configures systemd services for both standard and "everything" backup modes, and seeds backup database entries as needed.
Overview
Optimized for Archlinux, this role ensures that Docker volume backups are performed reliably with minimal manual intervention. It integrates with several dependent roles to verify backup success and manage related tasks, including:
- sys-svc-directory-validator – Validates backup directories.
- sys-ctl-cln-faild-bkps – Cleans up unsuccessful backup attempts.
- sys-timer – Schedules recurring backup tasks.
- sys-bkp-provider – Manages backup sources.
- sys-lock – Ensures coordinated maintenance operations.
Purpose
Backup Docker Volumes to Local is a comprehensive solution that leverages rsync to create incremental backups of Docker volumes, providing seamless recovery for both file and database data. Ideal for ensuring the integrity and security of your container data, this role sets up the necessary environment to safeguard your Docker volumes.
Features
- Required Software Installation: Installs necessary packages (e.g., lsof, python-pandas) via pacman.
- Git Repository Pull: Automatically pulls the latest version of the backup-docker-to-local.
- Systemd Service Configuration: Deploys and reloads two systemd service templates to manage backup tasks.
- Database Seeding: Includes tasks to seed and manage a backup database (
databases.csv) for tracking backup details. - Dependency Integration: Works in conjunction with the dependent roles listed above to verify and manage backups.