Sys-stk-front-base Role¶
Description: Front-layer base for web apps: HTTPS foundation, optional Cloudflare setup, and reverse-proxy handler wiring
Variables¶
author: Kevin Veen-Birkenbach
description: Front-layer base for web apps: HTTPS foundation, optional Cloudflare setup, and reverse-proxy handler wiring
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’, ‘https’, ‘cloudflare’, ‘automation’, ‘web’]
issue_tracker_url: https://s.infinito.nexus/issues
README¶
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-certif needed)
This role is intentionally small and reusable. It prepares the ground so app roles can just render their vHost.
Overview¶
This role front bootstrap for web apps: HTTPS base, optional Cloudflare setup, and handler wiring.
Cosmos¶
The diagram places Front Base (HTTPS + Cloudflare + Handlers) 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-base 💻]
svc_front_base["front-base"]
endSolid 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.
Features¶
Automated provisioning: Configured by Ansible without manual steps.
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
domainto be provided by the consumer
Outputs¶
Handler wiring completed
HTTPS base ready (NGINX, ACME webroot)
Cloudflare prepared (optional)
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).