Files
computer-playbook/roles/web-app-roulette-wheel
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
..
2025-11-27 19:02:44 +01:00

Roulette Wheel

Overview

This role deploys and configures the Roulette Wheel application using Docker Compose. It pulls the latest source code from a Git repository, builds a Docker image from a Node.js base, and starts the application on a user-defined local HTTP port.

Description

Roulette Wheel is a Node.js-based front-end application that is containerized using Docker. The role accomplishes the following:

  • Repository Integration: Automatically clones or updates the application repository from GitHub.
  • Dockerfile Management: Uses a custom Dockerfile (built on a Node.js image) to install dependencies, build the application, and define the startup command.
  • Container Deployment: Integrates with Docker Compose for container orchestration, making it easy to manage the application's lifecycle.

Features

  • Dockerized Deployment: Packages the application in a Docker container for consistent and isolated runtime.
  • Automated Builds: Uses an automated Docker build process with a dedicated Dockerfile.
  • Configurable Ports: Exposes the application through a customizable host port.
  • Git Integration: Ensures that the application source code is up-to-date by pulling from the specified Git repository.

Other Resources

Credits

Developed and maintained by Kevin Veen-Birkenbach.
Learn more at veen.world.
Licensed under the Infinito.Nexus NonCommercial License.