Post-Tyranny-Tech-Infrastru.../ansible/host_vars/specht.yml

---
# specht server - public network

# SSH directly via public IP
ansible_host: 188.245.122.208
ansible_ssh_private_key_file: ../keys/ssh/specht

# Client identification
client_name: specht
client_domain: specht.vrije.cloud
client_secrets_file: specht.sops.yaml
chore: Post-workshop state - January 23rd, 2026 This commit captures the infrastructure state immediately following the "Post-Tyranny Tech" workshop on January 23rd, 2026. Infrastructure Status: - 13 client servers deployed (white, valk, zwaan, specht, das, uil, vos, haas, wolf, ree, mees, mus, mol, kikker) - Services: Authentik SSO, Nextcloud, Collabora Office, Traefik - Private network architecture with edge NAT gateway - OIDC integration between Authentik and Nextcloud - Automated recovery flows and invitation system - Container update monitoring with Diun - Uptime monitoring with Uptime Kuma Changes include: - Multiple new client host configurations - Network architecture improvements (private IPs + NAT) - DNS management automation - Container update notifications - Email configuration via Mailgun - SSH key generation for all clients - Encrypted secrets for all deployments - Health check and diagnostic scripts Known Issues to Address: - Nextcloud version pinned to v30 (should use 'latest' or v32) - Zitadel references in templates (migrated to Authentik but templates not updated) - Traefik dynamic config has obsolete static routes 🤖 Generated with Claude Code (https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> 2026-01-23 20:36:31 +01:00			`---`
			`# specht server - public network`

			`# SSH directly via public IP`
			`ansible_host: 188.245.122.208`
			`ansible_ssh_private_key_file: ../keys/ssh/specht`

			`# Client identification`
			`client_name: specht`
			`client_domain: specht.vrije.cloud`
			`client_secrets_file: specht.sops.yaml`