mirror of https://github.com/kevinveenbirkenbach/computer-playbook.git synced 2025-12-10 11:26:24 +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

fix(svc-db-postgres): pin Postgres version to 17-3.5, add entity_name var, and dynamically resolve major version for dev package

2025-10-02 11:07:17 +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

filter_plugins

Implement filter checks: ensure all defined filters are used and remove dead code

2025-09-01 11:47:51 +02:00

README.md

PostgreSQL

Description

This Ansible role deploys and configures a PostgreSQL database in a Docker container using Docker Compose. It is designed to simplify database administration by automating the creation of networks, containers, and essential database tasks (such as database and user creation) for a secure and high-performance environment.

Overview

Built for environments that demand reliability and ease of management, this role:

Sets up a dedicated Docker network for PostgreSQL.
Deploys a PostgreSQL container with secure configurations and automated healthchecks.
Automates tasks like database creation, user setup, and privilege assignments to streamline your workflows.

Purpose

The purpose of this role is to provide an effortless way to deploy a PostgreSQL database via Docker. It minimizes manual interventions while ensuring that your database is configured securely and reliably for both production and development scenarios.

Features

Automated Deployment: Installs PostgreSQL with minimal manual steps.
Robust Administration: Automatically creates databases, users, and assigns privileges.
Enhanced Security: The service is bound to 127.0.0.1:5432, restricting access and enhancing security.
Seamless Docker Integration: Works harmoniously with Docker Compose and other roles in your infrastructure.

Credits 📝

Developed by Kevin Veen-Birkenbach.
Discover more at www.veen.world
Part of the Infinito.Nexus Project
License: Infinito.Nexus NonCommercial License