Document the ecosystem and add ingress fail2ban setup #3
Loading…
Reference in a new issue
No description provided.
Delete branch "codex/friend-installation-20260915"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds a reusable Caddy security-log snippet and guarded fail2ban jail installer for deployments with a separate HTTPS ingress. Exact hostname/login-path failures trigger nftables bans on TCP and UDP 80/443. The guide explains trustworthy client attribution, testing, recovery, CDN limitations and the need for native failure events for other applications.
Adds ecosystem guidance distinguishing this universal dashboard from game-specific dashboards and the blueprint generator. Version 0.8.0.
Validation: 16 Python tests including structured-log injection negatives, plus Bash syntax. The equivalent deployed ingress configuration passed a controlled failed-login ban/unban test, a forged-forwarding-header check, and IPv4/IPv6 ban persistence after a fail2ban restart.
Review branch only; merge before directing new users to the updated main-branch instructions. Credentials and private deployment state are excluded.