Infrastructure inventory
What runs where: nodes, services, and how they connect (high level, practical, and updated as it changes).
Nodes
Services
Topology
👋 About • Purpose • How this site is used
About this lab
dlbuild.net is my home lab build log. The goal is to learn real infrastructure skills by building, breaking, fixing, and documenting — with secure defaults and repeatable steps.
Document everything
Repeatable commands
Secure by default
Learn-by-doing
What you’ll find here
Labs + “fixed it” notes
Command snippets and case studies: errors encountered, what broke, and the exact steps used to recover.
Hands-on
Troubleshooting
Runbooks
Dashboard mindset
A quick “green-check” view: status checks and the first logs/commands to run when something looks off.
Ops
Health checks
Logs first
Projects roadmap
Planned builds that turn into write-ups: monitoring, hardening, automation, backups, and documentation.
Roadmap
Deliverables
Skills
How I work
My operating rules
- Admin tools stay private: access via VPN/internal routes only.
- Public access is static-only: publish the site, not the management plane.
- Small changes: one change at a time, verify, then document.
- Logs before guesses: check status and logs first, then troubleshoot.
My documentation pattern
- What changed: short summary of the action/goal
- Commands used: copy/paste block (working commands only)
- What broke: symptoms + error messages (exact text)
- Fix: confirmed steps + verification checks
Quick checks (first commands)
# validate nginx config and reload safely
sudo nginx -t && sudo systemctl reload nginx
# status checks (no pager)
sudo systemctl status nginx --no-pager
sudo systemctl status docker --no-pager
sudo systemctl status tailscaled --no-pager
sudo systemctl status cloudflared --no-pager
# resources
df -h
free -h
uptime
# containers
docker ps