0 Fork 0

mirror of https://github.com/kevinveenbirkenbach/computer-playbook.git synced 2026-11-06 10:59:59 +00:00

Files

T

kevinveenbirkenbachandClaude Opus 5 c55f508e05 feat(readme): draw mandatory and disabled service relations

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>

2026-08-17 18:02:31 +02:00

2.1 KiB

Raw Permalink Blame History

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.

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"]
    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

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

2.1 KiB Raw Permalink Blame History