Bilingual

I don't maintain my homelab, it maintains itself
25 days ago
- The author has automated their homelab to require minimal maintenance, achieving a self-maintaining setup.
- Infrastructure includes a single server and UniFi networking gear, both designed to update and run without manual intervention.
- Software maintenance is handled through a weekly Docker update cron job and automated backups, reducing hands-on time to about 15 minutes per month.
- This setup provides resilience, allowing the homelab to operate for extended periods without intervention, balancing privacy, security, and convenience.
Rebuilding My Homelab with Compose, Ruby, IPv6, and No Kubernetes
13 days ago
- The author's homelab had issues with a machine called 'nibbler' that was unreliable and likely defective, purchased as refurbished.
- Kubernetes was abandoned due to complexity and maintenance difficulties; the author reverted to using Docker Compose as a simpler solution.
- Current homelab setup includes: 'lrrr' (Proxmox host), 'morbo' (TrueNAS SCALE for storage), 'nibbler' (revamped as the main non-critical service machine), and an external VM 'ord-router' for public ingress.
- The deployment system uses Docker Compose stacks enhanced with Ruby libraries, Rake, and YAML for features like cron jobs, secrets management, ingress via Caddy, IPv6 networking, and cross-stack dependencies.
- Networking relies on deterministic IPv6 addressing with ULAs for isolation and security, and Caddy handles ingress with optional public exposure and authentication.
- Tailscale is used for secure backhaul traffic between hosts and for external access, though it causes battery drain on mobile devices.
- The architecture emphasizes failure domain separation: critical services on 'lrrr' and non-critical on 'nibbler' to minimize impact of failures.
- Full control over the system allows custom implementations (e.g., static sites via ingress, IPv6 setup) without relying on outdated external solutions.
- The author acknowledges that this setup may not suit everyone and validates alternatives like Kubernetes or other Docker Compose managers.
HomeLab #1: MikroTik as a Home Router
5 days ago
- Setting up a homelab begins with proper networking; MikroTik L009UiGS-RM is chosen for multiple Gigabit Ethernet ports and PoE capabilities.
- Before configuration, identify ISP setup: authentication method (IPoE or PPPoE) and IPv4 type (public vs. private/CGNAT).
- For PPPoE with VLAN, clone ISP router's MAC address on MikroTik's WAN port and create VLAN interface before PPPoE client setup.
- WiFi management uses separate wAP access point with PoE; RouterOS CAPsMAN centralizes configuration for multiple access points.
- Bufferbloat causes latency spikes during network saturation; implement FQ-CoDel queue discipline at 90-95% of line rate to reduce delays.
Kaizen #4: Overhauled Homelab
3 hours ago
- The author overhauled their homelab after moving to a new house, transitioning from a Zimaboard with NixOS to a more powerful HPE DL380 Gen10 server running Debian.
- They improved networking by installing Ubiquiti UniFi gear (UCG Ultra, three U7 Lite access points) and running Ethernet cables throughout the house, including to the garage, overcoming challenges like moving the fiber inlet to the attic.
- The new setup includes services like Jellyfin for media, Immich for photos, Syncthing for file sync, qBittorrent for downloads, Docker management via Dokploy, and monitoring with Uptime Kuma, Beszel, and Grafana/Loki.
- The old Zimaboard will be repurposed as a backup machine with Restic, and the author plans to add a GPU for local LLMs and explore VLANs in the future.

Hasty Briefsbeta

#homelab

I don't maintain my homelab, it maintains itself

Rebuilding My Homelab with Compose, Ruby, IPv6, and No Kubernetes

HomeLab #1: MikroTik as a Home Router

Kaizen #4: Overhauled Homelab