kevinveenbirkenbachandClaude Opus 5
c55f508e05
The cosmos generator linked a consumer to its provider only through an '<role>' in group_names reference or an explicit provides: name. A hard dependency has neither -- pinning the provider on unconditionally is exactly what removes the Jinja reference the generator was reading -- so web-svc-asset's bond to web-svc-file vanished from the diagram the moment it became binding. Match a service key against the provider's own primary key from the registry, in both directions. Services the role turns off drew a solid 1:1 edge, claiming a mandatory relationship for something that carries nothing at deploy time. They now render as a red 0..0 edge; edge merging gained a real precedence so a provider consumed through two keys stays live when only one is off. Named colour, not hex: a '#' opens an entity code in the mermaid lexer and turns the whole diagram into a parse error on GitHub. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Webserver HTTPS Provisioning
Description
The sys-svc-webserver-https role extends a basic NGINX installation by wiring in everything you need to serve content over HTTPS:
- Ensures your NGINX server is configured for SSL/TLS.
- Pulls in Let’s Encrypt ACME challenge handling.
- Applies global cleanup of unused domain configs.
This role is built on top of your existing sys-svc-webserver-core role, and it automates the end-to-end process of turning HTTP sites into secure HTTPS sites.
Overview
When you apply sys-svc-webserver-https, it will:
- Include the
sys-svc-webserver-corerole to install and configure NGINX. - Clean up any stale vHost files under
sys-svc-cln-domains. - Deploy the Let’s Encrypt challenge-and-redirect snippet from
sys-svc-letsencrypt. - Reload NGINX automatically when any template changes.
All tasks are idempotent. Once your certificates are in place and your configuration is set, Ansible will skip unchanged steps on subsequent runs.
Cosmos
The diagram places Webserver HTTPS Provisioning 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-webserver-https 💻]
svc_svc_webserver_https["svc-webserver-https"]
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.
Features
-
🔒 Automatic HTTPS Redirect
Sets up port 80 → 443 redirect and serves/.well-known/acme-challenge/for Certbot. -
🔑 Let’s Encrypt Integration
Pulls in challenge configuration and CAA-record management for automatic certificate issuance and renewal. -
🧹 Domain Cleanup
Removes obsolete or orphaned server blocks before enabling HTTPS. -
🚦 Handler-Safe
Triggers an NGINX reload only when necessary, minimizing service interruptions.
License
This role is released under the Infinito.Nexus Community License (Non-Commercial). See https://s.infinito.nexus/license for details.
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).