eblume/blumeops
1
1
Fork 0
Code Issues Pull requests Projects Releases 83 Packages Wiki Activity Actions
blumeops/docs/index.md
Erich Blume 4f0476a851
All checks were successful
Build Container / detect (push) Successful in 3s
Details
Build Container (Nix) / detect (push) Successful in 1s
Details
Build Container (Nix) / build (quartz) (push) Successful in 1s
Details
Build Container / build (quartz) (push) Successful in 10s
Details
Fix spider trap: disable SPA mode, remove index files, relax wiki-links (#290) 
## Summary

Fixes the Facebook crawler spider trap that's been generating infinite recursive URLs like `/how-to/tutorials/tutorials/how-to/explanation/...` for several days.

**Root cause:** Quartz SPA mode + nginx `try_files` fallback to `index.html` meant any fabricated URL returned the root HTML shell with HTTP 200. Crawlers followed relative links from those fake URLs, creating infinite recursion.

**Fix:**
- Disable Quartz SPA mode (`enableSPA: false`) — all pages are now fully static HTML
- Replace nginx SPA fallback with `=404` + Quartz's static `404.html`
- Remove `robots.txt` exclusions (no longer needed)

**Docs cleanup (Obsidian.nvim compat no longer needed):**
- Delete hand-curated category index files (`tutorials.md`, `reference.md`, `how-to.md`, `explanation.md`) — Quartz auto-generates folder pages
- Delete `postgresql-storage.md` (redirect stub) and `migrate-forgejo-from-brew.md` (stale history)
- Drop `docs-check-index` and `docs-check-filenames` prek hooks
- Rewrite `docs-check-links` to allow path-based wiki-links (`[[path/to/file]]`) and only error on true ambiguity
- Add `ai-docs` doc tree listing to replace index files for AI context
- Add natural cross-links from reference cards to fix orphan docs

## Deployment and Testing

- [ ] Merge and let the build pipeline run
- [ ] Verify docs.eblu.me serves pages correctly with full page loads
- [ ] Verify non-existent URLs return 404
- [ ] Monitor crawler traffic — should drop to near zero for fabricated URLs

Reviewed-on: #290
2026-03-09 11:59:43 -07:00

1.9 KiB
Raw Permalink Blame History

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