2026-02-03 09:13:50 -08:00
|
|
|
---
|
2026-02-07 21:26:18 -08:00
|
|
|
title: BlumeOps
|
2026-02-11 16:45:12 -08:00
|
|
|
modified: 2026-02-08
|
2026-02-07 21:02:10 -08:00
|
|
|
aliases: []
|
|
|
|
|
id: index
|
|
|
|
|
tags: []
|
2026-02-03 09:13:50 -08:00
|
|
|
---
|
|
|
|
|
|
2026-02-07 21:02:10 -08:00
|
|
|
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.
|
2026-02-03 09:13:50 -08:00
|
|
|
|
2026-02-03 18:51:57 -08:00
|
|
|
**New here?** Start with [[exploring-the-docs]] to find your way around.
|
2026-02-03 14:32:59 -08:00
|
|
|
|
2026-02-07 21:02:10 -08:00
|
|
|
## What is BlumeOps?
|
|
|
|
|
|
|
|
|
|
BlumeOps is my personal homelab infrastructure managed entirely through code.
|
2026-02-07 21:26:18 -08:00
|
|
|
Everything lives in a [single git repository](https://github.com/eblume/blumeops), from service configs to
|
Expose Forgejo publicly at forge.eblu.me (#278)
## Summary
Expose Forgejo publicly at `forge.eblu.me` via the Fly.io reverse proxy — the first dynamic, authenticated public-facing service.
- **Forgejo hardening:** Domain changed to forge.eblu.me, SSH stays on forge.ops.eblu.me, reverse proxy trust headers configured, local registration locked to external-only (Authentik SSO)
- **Tailscale Ingress:** ExternalName Service + Ingress in tailscale-operator creates forge.tail8d86e.ts.net endpoint
- **Fly.io proxy:** nginx server block with rate-limited auth endpoints (3r/s), fail2ban with custom nginx-deny action, security headers, /swagger blocked, WebSocket support, 512m body limit
- **Authentik:** OAuth callback updated to forge.eblu.me
- **DNS/TLS:** CNAME record in Pulumi, cert in fly-setup
- **Rename:** ~29 files updated from forge.ops.eblu.me to forge.eblu.me (HTTPS refs only; SSH, container builds, and Caddy table kept as-is)
## Deployment Order
1. `mise run provision-indri -- --tags forgejo` (config changes)
2. Verify forge.ops.eblu.me still works
3. `argocd app set tailscale-operator --revision feature/forge-public && argocd app sync tailscale-operator`
4. Verify `curl https://forge.tail8d86e.ts.net`
5. `cd fly && fly deploy`
6. Verify pre-DNS: `curl -H "Host: forge.eblu.me" https://blumeops-proxy.fly.dev/`
7. `fly certs add forge.eblu.me -a blumeops-proxy`
8. `argocd app set authentik --revision feature/forge-public && argocd app sync authentik`
9. `mise run dns-preview && mise run dns-up`
10. Full verification (see below)
11. Rehearse `mise run fly-shutoff`
12. After merge: reset ArgoCD revisions to main, re-sync
## Verification Checklist
- [ ] forge.eblu.me loads, shows public repos
- [ ] forge.ops.eblu.me still works from tailnet
- [ ] SSH clone via forge.ops.eblu.me:2222 works
- [ ] HTTPS clone via forge.eblu.me works
- [ ] UI shows forge.eblu.me for HTTPS clone, forge.ops.eblu.me for SSH
- [ ] /swagger returns 403
- [ ] Rapid login attempts trigger 429 rate limit
- [ ] fail2ban bans after 5 failed logins in 10 minutes
- [ ] ArgoCD can still sync (SSH unaffected)
- [ ] `mise run fly-shutoff` stops all public traffic
- [ ] `mise run services-check` passes
Reviewed-on: https://forge.eblu.me/eblume/blumeops/pulls/278
2026-03-03 08:40:41 -08:00
|
|
|
deployment automation. Even the [[forgejo]] instance that [hosts this repo](https://forge.eblu.me/eblume/blumeops)
|
2026-02-07 21:26:18 -08:00
|
|
|
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.)
|
2026-02-07 21:02:10 -08:00
|
|
|
|
|
|
|
|
These services run on my home [[hosts|infrastructure]], primarily an m1 mac
|
|
|
|
|
mini named [[indri]] and a Synology NAS called [[sifaka]]. The infrastructure
|
2026-02-08 02:36:19 -08:00
|
|
|
is networked via [[tailscale]], with the domain `eblu.me` hosted via [[gandi]],
|
|
|
|
|
[[caddy]] providing a private reverse proxy for tailnet devices, and
|
|
|
|
|
[[flyio-proxy|Fly.io]] serving public-facing services like
|
|
|
|
|
[this documentation site](https://docs.eblu.me).
|
2026-02-07 21:02:10 -08:00
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
2026-02-03 14:32:59 -08:00
|
|
|
## Sections
|
|
|
|
|
|
2026-02-04 17:21:34 -08:00
|
|
|
- [[tutorials|Tutorials]] - Learning-oriented guides for getting started
|
|
|
|
|
- [[reference|Reference]] - Technical specifications and service details
|
|
|
|
|
- [[how-to|How-to]] - Task-oriented instructions for common operations
|
|
|
|
|
- [[explanation|Explanation]] - Understanding the "why" behind BlumeOps
|
2026-02-04 08:13:16 -08:00
|
|
|
- [[CHANGELOG]] - Release history and changes
|