Docker-first starter stack
Updated 2026-07-18 · 8 min read · By Ben Liu
Compose-friendly picks for reverse proxy, vault, photos, and a homepage — a practical first rack.
Who this stack is for
Choose this collection if you already know Docker Compose basics and want one coherent first rack: TLS entrypoint, password vault, photo backup, and a status homepage.
It prioritizes rebuildability over exotic features. Every piece should be replaceable without rewriting your entire mental model.
Deploy order that reduces pain
Start with Caddy (or another reverse proxy) and DNS. Add Vaultwarden next so secrets are not scattered in notes. Bring Immich online only after volumes and backup targets exist. Finish with Homepage so the family can find services without asking you.
Do not expose admin panels publicly on day one. Use VPN or SSO hooks once the stack is stable on the LAN.
Failure modes to plan for
Disk fills during Immich thumbnails, Vaultwarden backups never get restored, and Homepage links rot after renames. Schedule a monthly restore drill and a link audit.
Projects in this collection
Tools in this stack are listed for context. This column leads with guides — open each project only when you need a deeper lab note.
Caddy
Powerful, enterprise-ready, open source web server with automatic HTTPS.
Vaultwarden
Lightweight Bitwarden server API implementation written in Rust.
Immich
Photo and video backup solution directly from your mobile phone (alternative to Google Photos).
Homepage by gethomepage
Highly customizable homepage (or startpage / application dashboard) with Docker and service API integrations.