Corbin Infrastructure

The operating record for Corbin's VPS, home server, public services, and recovery process.

Start Here

Need	Go to
Find a service or its URL	Home services
See what runs where	Service catalog
Understand where things run	Architecture
Restore something	Backups and restore
Recover under pressure	Recovery card
Rebuild after a major failure	Disaster recovery runbook
Check access and exposure	Security baseline
Find a hostname or DNS role	Domain layout
See what changed	Change log
Pick the next improvement	Backlog
Track an idea, task, or incident	Work tracking
Understand the local AI assistant	AI assistant
Operate or restore the fax portal	Fax portal
Connect remotely to home services	WireGuard remote access
Connect to an Ubuntu host over SSH	SSH access
Operate the NWOMS quizzes and staff survey	QuizDock and LimeSurvey operations

Current Estate

Location	Purpose	Entry point
corbin-edge	Public support site, mail, RustDesk, secure sharing, Vaultwarden, and monitoring	corbinishelpingyou.online
corbin-media	Media, documents, Git, automation, network services, and personal tools	192.168.4.103
corbin-core	Fax portal, local AI experiments, and encrypted recovery replica	192.168.4.105
Forgejo	Versioned configuration and documentation	https://git.corbinishelpingyou.online
Homepage	LAN service launchpad and health checks	http://192.168.4.103:3002

Working Rules

• Never commit passwords, private keys, API tokens, Wi-Fi credentials, database dumps, or filled .env files.
• Back up before changing a live service, validate configuration before restart, then verify the result.
• Keep public services on the VPS unless there is a deliberate reason to expose a home-hosted service.
• Treat Git as the intended configuration record, not as a replacement for Restic backups.
• Create an issue for an idea, incident, or maintenance task before it becomes a vague memory.

Daily Commands

cd ~/corbin-infrastructure
git status
docker ps
systemctl list-timers --all

/home/corbin/corbin-infrastructure on corbin-media is the only supported working checkout. Semaphore mounts that same checkout read-only. Dated or legacy directories must not be used for automation or treated as current documentation.

Repository Layout

• compose/ - reproducible Docker Compose definitions and non-secret configuration.
• ansible/ - home-server automation playbooks managed through Semaphore.
• docs/ - operational notes, recovery procedures, service maps, and change history.
• scripts/ - checked-in helper scripts; credentials stay on the hosts.
• systemd/ - timers and service definitions that keep recurring jobs visible.

Before You Change Anything

1. Read the matching service and recovery documentation.
2. Create a focused issue if the work is not a quick repair.
3. Make a backup or confirm the scheduled backup is current.
4. Verify locally, then verify the public hostname only when that service is intentionally public.
5. Update the change log and commit the non-secret configuration.