Sys-stk-front-proxy Role

Description: Orchestration wrapper for per-domain NGINX provisioning with TLS certificates, vHost templates, and optional OAuth2

Variables

  • author: Kevin Veen-Birkenbach

  • description: Orchestration wrapper for per-domain NGINX provisioning with TLS certificates, vHost templates, and optional OAuth2

  • 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: [‘nginx’, ‘tls’, ‘letsencrypt’, ‘oauth2’, ‘automation’, ‘archlinux’]

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

README

NGINX Domain Setup

Description

This role bootstraps per-domain NGINX configuration: it requests TLS certificates, applies global modifiers, deploys a ready-made vHost file, and can optionally lock down access via OAuth2.

Overview

A higher-level orchestration wrapper, sys-stk-front-proxy ties together several lower-level roles:

  1. ``sys-front-inj-all`` – applies global tweaks and includes.

  2. ``sys-svc-certs`` – obtains Let’s Encrypt certificates.

  3. Domain template deployment – copies a Jinja2 vHost from sys-svc-proxy.

  4. ``web-app-keycloak``’s SSO-proxy sidecar (optional) – protects the site with OAuth2.

The result is a complete, reproducible domain rollout in a single playbook task.

Cosmos

The diagram places NGINX Domain Setup 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-stk-front-proxy 💻]
        svc_front_proxy["front-proxy"]
    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

Provide one-stop, idempotent domain provisioning for NGINX-based homelabs or small production environments.

Features

  • End-to-end TLS: certificate retrieval and secure headers included.

  • Template-driven vHosts: choose basic or ws_generic flavours (or your own).

  • Conditional OAuth2: easily toggle authentication per application.

  • Handler-safe: automatically triggers an NGINX reload when templates change.

  • Composable: designed to be called repeatedly for many domains.

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).