Sergei Poljanski
27ccdc4255
The roles had drifted far from production: Forgejo was pinned at 12 while 15.0.11 runs, its config lacked the mailer, packages and the real database path, and several services existed only on the hosts. Running a role would have rolled production back. Take the servers as the truth and make the repository match them. site.yaml now holds the desired state of both hosts: - base: unattended upgrades, fail2ban, Docker daemon config and the weekly image prune, as found on the hosts. New: a 500M journal cap, and the Docker systemd override is kept absent. That override once opened dockerd on tcp/2375 without authentication. - traefik: templates as deployed, version in a variable (v3.7.18). The Coraza WAF files are removed; no router ever used them. - forgejo: 15.0.11, app.ini generated from the live file with the secrets taken from the vault. - crawler_alert, sillytavern, minecraft, minecraft_fossils: added from the hosts. Forgejo's canonical name becomes git.asxp.io; git.czsk.it stays as an alias on the same router. docker_service restarts a stack when its config changes, no longer forces ownership on existing data directories, and hides template diffs because they carry secrets. Containers listed in service_graceful_stop are saved and stopped with a long timeout before compose recreates them: Docker's 10 s default is too short for a Minecraft world. Both game servers get stop_grace_period for the same reason. Removed: the full-deployment and runner playbooks with their prompts, the Forgejo backup and restore roles for the old bare-metal host, and inventory entries for services that were never deployed. SSH hardening stays a manual playbook, since a mistake there locks everyone out. New secrets (SMTP, RCON, CurseForge key) went into the vault. Assisted-by: Claude:fable-5-2 |
||
|---|---|---|
| .. | ||
| inventory | ||
| playbooks | ||
| roles | ||
| .gitignore | ||
| ansible.cfg | ||
| README.md | ||
| site.yaml | ||
ASXP.IO Ansible Infrastructure
Automated deployment for asxpio servers: WireGuard VPN, SSH hardening, Traefik, Forgejo, and S3 storage.
Quick Start
# 1. Setup vault
echo "your-password" > .vault_pass && chmod 600 .vault_pass
./scripts/setup-vault.sh encrypt
# 2. Stage 1: WireGuard VPN
ansible-playbook playbooks/01-wireguard-setup.yaml
# Connect to VPN, update inventory/hosts.yaml to use WireGuard IPs
# 3. Stage 2: Full deployment (SSH hardening, Traefik, Forgejo, Runner)
ansible-playbook playbooks/02-full-deployment.yaml
# 4. Stage 3: S3 storage mounts
ansible-playbook playbooks/03-setup-s3fs.yaml
Infrastructure
Servers:
- asxpio-ops (CX22): Forgejo, Traefik, WireGuard VPN hub
- asxpio-services (CX43): Forgejo Runner, Immich, game servers
Networks:
- VPC: 10.10.0.0/20
- WireGuard: 10.20.0.0/24
S3 Buckets (mounted via s3fs):
- asxpio-terraform-main → /mnt/s3/terraform
- asxpio-backups-main → /mnt/s3/backups
- asxpio-immich-main → /mnt/s3/immich
Playbook Workflow
- WireGuard Setup - Deploy VPN, generate client configs
- Full Deployment - SSH hardening (no lockout), Traefik, Forgejo, Runner
- S3 Storage - Mount S3 buckets with automatic cache management
All playbooks are idempotent - safe to rerun without breaking existing setup.
Configuration Files
inventory/
├── hosts.yaml # Server inventory, IPs, groups
├── group_vars/all/ # Variables applied to all hosts
│ ├── main.yaml # Forgejo version, ports, runner config
│ ├── network.yaml # VPC (10.10.0.0/20), WireGuard (10.20.0.0/24) IPs
│ ├── services.yaml # Service paths (/opt/*), ports, Docker networks
│ ├── s3.yaml # S3 buckets, mount points, credentials reference
│ └── vault.yaml # ENCRYPTED: S3 keys, Forgejo secrets, runner token
└── host_vars/ # Host-specific overrides
├── asxpio-ops.yaml # WireGuard server, clients list, S3 cache: 10GB
└── asxpio-services.yaml # S3 cache: 80GB