JB Infrastructure — Map of the Kingdom¶
This repo is the single source of truth for the JB Hostinger VPS infrastructure: what runs, how it connects, and how it is operated.
Application documentation lives inside each application repo under /docs/. This repo covers the shared infrastructure that all applications depend on.
Last updated: 2026-05-11
Quick navigation¶
| What you need | Where to look |
|---|---|
| What is this VPS, what does it cost, when does it expire | vps-overview.md |
| What containers run, organised by function | docker-layout.md |
| Ports, firewall, domains, nginx, TLS | networking.md |
| Postgres setup, databases, retention | postgres.md |
| Backup strategy and known gaps | backups.md |
| Monitoring stack and alerts | monitoring.md |
| Security posture (UFW, Falco, ClamAV, Vaultwarden) | security.md |
| How to deploy and promote dev → staging → prod | deployment-process.md |
| What to do when things break | incident-response.md |
| First week as a new team member | onboarding.md |
| Why we built things the way we did | adr/ |
Reading order for new joiners¶
- onboarding.md — start here
- vps-overview.md — the hardware and the plan
- docker-layout.md — what is running
- networking.md — how it connects to the outside world
- adr/ — the decisions that shaped everything else
Conventions¶
- Markdown only. No DOCX, no PDF, no proprietary formats.
- AUTO-GENERATED sections are marked with
<!-- AUTO-GENERATED -->and<!-- /AUTO-GENERATED -->. Do not edit by hand — thedocument.infra-scannerskill owns them. - Manual sections are owned by humans and reflect intent, context, rationale.
- ADRs are immutable once accepted. New decisions get new ADR numbers; they may supersede older ones.
- Sovereignty first. No external SaaS for code, secrets, or docs. Everything self-hosted.