Sys-stk-semi-stateless Role¶
Description: No description available
Variables¶
author: Kevin Veen-Birkenbach
description: Combined semi-stateless app stack: front bootstrap + stateless backend.
license: Infinito.Nexus NonCommercial License
license_url: https://s.infinito.nexus/license
company: Kevin Veen-Birkenbach
Consulting & Coaching Solutions https://www.veen.world
min_ansible_version: 2.9
platforms: [{‘name’: ‘Archlinux’, ‘versions’: [‘rolling’]}]
galaxy_tags: [‘nginx’, ‘https’, ‘stateless’, ‘backend’, ‘cloudflare’, ‘automation’]
repository: https://s.infinito.nexus/code
issue_tracker_url: https://s.infinito.nexus/issues
documentation: https://docs.infinito.nexus/
README¶
Semi-Stateless Stack (Front + Back) ⚡¶
Description¶
sys-stk-semi-stateless combines the front and back layer into a
lightweight, mostly stateless web service stack: - Front bootstrap via
sys-stk-front-base (HTTPS base, optional Cloudflare, handlers) -
Backend via sys-stk-back-stateless (no persistent volumes/DB)
Ideal for services that need TLS/front glue but no database (e.g., TURN/STUN, gateways, simple APIs).
Responsibilities¶
Prepare the front layer (HTTPS / handlers / optional Cloudflare)
Deploy the stateless backend (typically via Docker Compose)
Keep domain variables (
domain) and app-scoped variables (application_id) clearly separated