Homelab notes

Notes on the applications, networking, and maintenance of my homelab.

Build a practice homelab

• Build your first homelab →

  Start with a fresh Linux machine, then run, inspect, and restore a small Compose project.

• Install Docker and Compose →

  Prepare a fresh Ubuntu practice server and verify Docker before adding applications.

• Run the practice lab →

  Download the example, create a local secret, start three services, and check the result.

• Understand the Compose settings →

  What each part of the practice configuration does, and which settings need care.

• Follow a request through DNS and Traefik →

  Separate name resolution, published ports, routing, and application responses.

• Diagnose a stack without resetting it →

  Inspect configuration, process state, routes, logs, and disk space before changing anything.

• Back up a file and prove you can restore it →

  Create an encrypted restic repository and compare a restored file with its source.

• Add one stack at a time →

  Choose an application, separate its configuration and data, and document recovery before expanding.

• How my homelab fits together →

  What belongs in apps, core, and ops, with an example from this website.

Groups

• Apps: applications →

  Photo and file storage, media, automation, and other applications.

• Core: networking and access →

  DNS, web routing, sign-in, remote access, and traffic protection.

• Ops: operations and maintenance →

  Backups, monitoring, logs, notifications, and system administration.

The catalogs describe the repository structure. Entries may be inactive or private; host configuration and procedures are included alongside container stacks.