mirror of https://github.com/kevinveenbirkenbach/computer-playbook.git synced 2025-12-09 10:56:01 +00:00

Files

Kevin Veen-Birkenbach 716ebef33b Refactor task includes and update variable handling for Ansible 2.20 migration

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

2025-12-03 11:02:34 +01:00

config

feat(services): add CPU/RAM/PIDs defaults for heavy roles and align service names

2025-09-23 21:43:50 +02:00

defaults

Refactor DB initialization handling: externalize database_init flag for svc-db-mariadb and svc-db-postgres, remove internal auto-detection, and pass explicit init signal from sys-stk-back-stateful. Improves clarity, avoids incorrect credential lookups, and stabilizes central DB setup.

2025-12-01 20:40:30 +01:00

README.md

MariaDB

Overview

This Ansible role facilitates the deployment of a MariaDB server using Docker. It is designed to ensure ease of installation and configuration, with the flexibility to adapt to different environments.

Features

Dockerized MariaDB: Leverages Docker for MariaDB deployment, ensuring consistency across different environments.
Customizable Settings: Allows customization of the MariaDB instance through various Ansible variables.
Network Configuration: Includes setup of a dedicated Docker network for MariaDB.
Idempotent Design: Ensures that repeat runs of the playbook do not result in unwanted changes.
Security Focused: Implements best practices for securing the MariaDB root password.

Prerequisites

Before using this role, ensure you have the following:

Ansible installed on the control machine.
Docker installed on the target host(s).
Access to the target host(s) via SSH.

Configuration

Configure the role by setting the required variables. These can be set in the playbook or in a separate variable file:

central_mariadb_root_password: The root password for the MariaDB server.
database_name: The name of the initial database to create.
database_username: The username for the database user.
database_password: The password for the database user.

Contributing

Contributions to this project are welcome. Please submit issues and pull requests with your suggestions.

Further Resources

Reset Password for MariaDB/MySQL in Docker