Erich Blume
1c32e351f7
Dagger's --src=. excludes .git, so Quartz can't use git history for page dates inside containers. Populate date-modified: YYYY-MM-DD in frontmatter for all 80 doc articles so the frontmatter priority level (highest in quartz.config.ts) works with or without git. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1.9 KiB
| title | date-modified | aliases | id | tags |
|---|---|---|---|---|
| BlumeOps | 2026-02-08 | index |
Welcome to the BlumeOps (aka "Blue Mops") documentation. Here you will find hopefully everything you'll need to understand and operate my personal digital infrastructure.
New here? Start with exploring-the-docs to find your way around.
What is BlumeOps?
BlumeOps is my personal homelab infrastructure managed entirely through code. Everything lives in a single git repository, from service configs to deployment automation. Even the forgejo instance that hosts this repo is defined within it, making BlumeOps fully self-hosting. It's a digital life raft I built for myself as I went, and you can see it all from within your editor of choice. (I recommend vim.)
These services run on my home hosts, primarily an m1 mac
mini named indri and a Synology NAS called sifaka. The infrastructure
is networked via tailscale, with the domain eblu.me hosted via gandi,
caddy providing a private reverse proxy for tailnet devices, and
flyio-proxy serving public-facing services like
this documentation site.
The goal of BlumeOps is threefold:
- To provide a rich array of useful personal services in order to manage my own digital life.
- To exercise my skills as a software engineer specializing in Platforms/DevOps/SRE.
- To act as a portfolio piece for talking about building hosted software platforms.
Sections
- tutorials - Learning-oriented guides for getting started
- reference - Technical specifications and service details
- how-to - Task-oriented instructions for common operations
- explanation - Understanding the "why" behind BlumeOps
- CHANGELOG - Release history and changes