blumeops/docs/index.md
Erich Blume 251873906a Disable SPA mode, remove index files, relax wiki-link constraints
Fix the Facebook crawler spider trap by disabling Quartz SPA mode and
removing the nginx fallback to index.html. Non-existent URLs now return
404.html instead of the root SPA shell, preventing infinite recursive
crawling.

Remove hand-curated category index files (tutorials.md, reference.md,
how-to.md, explanation.md) — Quartz auto-generates folder pages. Drop
docs-check-index and docs-check-filenames hooks. Update docs-check-links
to allow path-based wiki-links and only error on true ambiguity. Remove
robots.txt exclusions since they're no longer needed.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-09 11:57:35 -07:00

1.9 KiB

title 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:

  1. To provide a rich array of useful personal services in order to manage my own digital life.
  2. To exercise my skills as a software engineer specializing in Platforms/DevOps/SRE.
  3. 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