Files
computer-playbook/roles/sys-stk-front-base
Kevin Veen-Birkenbach e09f561f0b Refactor run-once orchestration and bootstrap Mailu/Mastodon in a single deploy
- Replace legacy utils/run_once.yml with the new helpers utils/once_flag.yml and utils/once_finalize.yml
- Introduce utils/compose_up.yml to ensure docker-compose stacks are up and to flush handlers safely without coupling to run-once flags
- Migrate all affected roles (desk-*, dev-*, sys-ctl-*, sys-svc-*, web-app-*, web-svc-*, util-*) to the new run-once helpers
- Rework sys-svc-msmtp to auto-load Mailu once per deploy, check reachability, and reuse the running stack instead of requiring multiple playbook passes
- Adjust web-app-mailu to integrate cert deployment, handler flushing, and run-once handling so Mailu is fully initialized in a single deploy
- Improve Matomo, CDN, logout and CSP/health-check related roles to cooperate with the new compose_up / once_* pattern
- Simplify alarm/backup/timer/service orchestration (sys-ctl-alm-*, sys-bkp-provider, sys-timer-cln-bkps, etc.) by moving run-once logic into dedicated 01_core.yml files
- Update integration tests so utils/once_flag.yml and utils/once_finalize.yml are recognised as valid run-once providers, keeping the global run_once_* guarantees consistent
- Align frontend injection and service dependencies so Mastodon- and Mailu-related services can be brought up coherently within a single deployment cycle rather than several iterations
2025-12-01 13:30:50 +01:00
..

Front Base (HTTPS + Cloudflare + Handlers) 🚀

Description

sys-stk-front-base bootstraps the front layer that most web-facing apps need:

  • Ensures the HTTPS base via sys-svc-webserver-https
  • (Optional) Cloudflare bootstrap (zone lookup, dev mode, purge)
  • Wires OpenResty/Nginx handlers
  • Leaves per-domain certificate issuance to consumer roles (or pass-through vars to sys-util-csp-cert if needed)

This role is intentionally small and reusable. It prepares the ground so app roles can just render their vHost.

Responsibilities

  • Include sys-svc-webserver-https (once per host)
  • Include Cloudflare tasks when DNS_PROVIDER == "cloudflare"
  • Load handler utilities (e.g., svc-prx-openresty)
  • Stay domain-agnostic: expect domain to be provided by the consumer

Outputs

  • Handler wiring completed
  • HTTPS base ready (Nginx, ACME webroot)
  • Cloudflare prepared (optional)