mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-08 19:56:53 +00:00
kevinveenbirkenbachandClaude Opus 5
7bc12e55f3
aceb5295efmoved Cosmos, Quick Setup and Credits out of the committed role READMEs and into the documentation build's own scratch checkout, so a committed copy can no longer go stale when the metadata moves. Merging feature/designer (ebad39422c) took origin/main's side of those files, which still carries them, and reinstated all 290 along with the cosmos make target and its i8cos alias. tests/lint/ansible/roles/test_readme.py hard-fails on a committed copy, and the reinstated Credits block credited one person with two URLs, which tripped the credits-attribution lint as well. Stripped with the repository's own fence-aware parser against MANAGED_SECTIONS, not with a line filter: the Cosmos block holds a mermaid fence a naive filter would cut through. The result is byte-identical toaceb5295effor every README that carries no prose change since. The cosmos target wrote the forbidden section straight back into the checkout, so it goes with them. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
48 lines
1.7 KiB
Markdown
48 lines
1.7 KiB
Markdown
# 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:
|
||
|
||
1. Ensures your NGINX server is configured for SSL/TLS.
|
||
2. Pulls in Let’s Encrypt ACME challenge handling.
|
||
3. 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:
|
||
|
||
1. **Include** the `sys-svc-webserver-core` role to install and configure NGINX.
|
||
2. **Clean up** any stale vHost files under `sys-svc-cln-domains`.
|
||
3. **Deploy** the Let’s Encrypt challenge-and-redirect snippet from `sys-svc-letsencrypt`.
|
||
4. **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.
|
||
|
||
---
|
||
|
||
## 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](https://s.infinito.nexus/license) for details.
|