Sys-svc-compose Role

Description: Infrastructure role for managing containerized-application project structures, .env files, and lifecycle handlers

Variables

  • author: Kevin Veen-Birkenbach

  • description: Infrastructure role for managing containerized-application project structures, .env files, and lifecycle handlers

  • license: Infinito.Nexus Community License (Non-Commercial)

  • company: Kevin Veen-Birkenbach https://www.veen.world

  • min_ansible_version: 2.9

  • platforms: [{‘name’: ‘ArchLinux’, ‘versions’: [‘all’]}, {‘name’: ‘Debian’, ‘versions’: [‘all’]}, {‘name’: ‘EL’, ‘versions’: [‘all’]}, {‘name’: ‘Fedora’, ‘versions’: [‘all’]}, {‘name’: ‘Ubuntu’, ‘versions’: [‘all’]}]

  • galaxy_tags: [‘docker’, ‘compose’, ‘container’, ‘infrastructure’, ‘devops’, ‘automation’, ‘archlinux’]

  • issue_tracker_url: https://s.infinito.nexus/issues

README

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 compose.yml files, and provides automation logic for project reset, rebuild, and startup sequences.

Refer to the Docker Compose documentation and the Arch Wiki – Docker 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.

Cosmos

The diagram places Docker Compose in the Infinito.Nexus cosmos: the components it deploys (capabilities), the central services it consumes (dependencies), and its outward reach (federation and bridged external networks).

flowchart LR
    subgraph role [sys-svc-compose 💻]
        svc_svc_compose["svc-compose"]
    end

Solid 1:1 edges are fixed relationships; dashed 0..1 edges are conditional (enabled only in matching deployments); red 0..0 edges are turned off in this role. Node markers show the role’s deploy modes (💻 host, 🐳 compose, 🐝 swarm); ❌ marks a service that is explicitly turned off, and ⚙️ an Ansible role dependency declared in meta/main.yml.

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_RESET is enabled.

  • Handlers for Runtime Control: Automatically builds, sets up, or restarts containers based on handlers. Notify compose up when rendered files or the service spec changed; notify container recreate when only in-container or in-database state changed and the process must reload it — the latter force-recreates in compose mode and forces a task recreation in swarm mode, where docker stack deploy alone would leave the running task untouched.

  • Template-ready Service Files: Predefined service base and health check templates.

  • Integration Support: Compatible with sys-svc-proxy and other Infinito.Nexus service roles.

Credits

Implemented by Kevin Veen-Birkenbach. Part of the Infinito.Nexus Project and maintained by Kevin Veen-Birkenbach. Licensed under the Infinito.Nexus Community License (Non-Commercial).