blumeops/CLAUDE.md

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Project Overview

blumeops is Erich Blume's GitOps repository for personal infrastructure management, orchestrated via tailnet tail8d86e.ts.net.

Critical: This repository is published publicly at https://github.com/eblume/blumeops, so never include any secrets!

Rules

1. At the start of every session, even if the user asked to do something else, run mise run zk-docs -- --style=header --color=never --decorations=always in order to review the blumeops documentation in the zettelkasten (zk). zk lives at ~/code/personal/zk, and is managed via obsidian-sync (not git).

2. When making any changes, start by making sure you're on the main git branch and up-to-date, and then create a feature branch. Commit often while working, and create a PR using:

tea pr create --title "Description of change" --description "$(cat <<'EOF'
## Summary
- First change
- Second change

## Deployment and Testing
- [x] Done thing one
- [ ] Needed thing two

🤖 Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"

The user will review your work as you go, and will merge the pr as the last step in the process, even after deploying.

3. Always keep the zk cards up to date with any changes, and suggest new links to new cards whenever appropriate. Refer back to the zk docs often during the process of planning and making corrections to ensure accuracy, and if you make a mistake, figure out a way to guard against it using the zk.

4. Use Brewfile and mise.toml to install tools needed on the development workstation (typically hostnamed "gilbert", username "eblume").

5. Services are hosted either on indri directly (via ansible) or in Kubernetes (via ArgoCD). See the "Service Deployment" section below for details.

6. Try to always test changes before applying them. Use syntax checkers, do dry runs (--check --diff), run commands manually via ssh indri 'some command', etc.

7. Wait for user review before deploying. After creating a PR, do not run deployment commands until the user has had a chance to review the changes. The user will indicate when they're ready to deploy.

8. After deploying changes, try to verify the result. Use mise run indri-services-check to do a general service health check.

Project Structure

./mise-tasks/           # management and utility scripts run via `mise run`
./ansible/playbooks/    # ansible playbooks (indri.yml is primary)
./ansible/roles/        # ansible roles for indri-hosted services
./argocd/apps/          # ArgoCD Application definitions (app-of-apps pattern)
./argocd/manifests/     # Kubernetes manifests for each service
./pulumi/               # Pulumi IaC for tailnet ACLs and cloud resources
./plans/                # Migration and project planning documents
~/code/personal/        # projects managed by the user
~/code/3rd/             # external projects, mirrored or downloaded
~/code/work             # FORBIDDEN, never go here, avoid searching it

Service Deployment

Kubernetes Services (via ArgoCD)

Most services are migrating to Kubernetes. These are managed via ArgoCD using the app-of-apps pattern:

• Application definitions: argocd/apps/<service>.yaml
• Manifests: argocd/manifests/<service>/
• Sync policy: Manual sync (no auto-sync on git push)

PR workflow for k8s services:

1. Create feature branch and add/modify manifests
2. Push branch to forge
3. Sync the apps application to pick up new Application definitions:

   argocd app sync apps
   

4. Point the service app at the feature branch for testing:

   argocd app set <service> --revision feature/branch-name
   argocd app sync <service>
   

5. Test the deployment
6. After PR merge, reset to main and resync:

   argocd app set <service> --revision main
   argocd app sync <service>
   

Useful commands:

argocd app list                                        # List all apps
argocd app get <app>                                   # Get app details
argocd app diff <app>                                  # Preview changes before sync
argocd app sync <app>                                  # Sync an app
kubectl --context=minikube-indri get pods -n <namespace>  # Check pods
kubectl --context=minikube-indri logs -n <namespace> <pod>  # View logs

Note: The user has fish abbreviations ki for kubectl --context=minikube-indri and k9i for k9s --context=minikube-indri, but these only work in interactive shells.

Indri Services (via Ansible)

Some services remain on indri outside of Kubernetes:

• Zot Registry - Container registry (k8s depends on it)
• Prometheus/Loki - Observability (must survive k8s failures)
• Borgmatic - Backup system
• Grafana Alloy - Metrics/logs collector
• Transmission - BitTorrent for kiwix downloads

Deployment:

mise run provision-indri                    # Full playbook
mise run provision-indri -- --tags <role>   # Specific role
mise run provision-indri -- --check --diff  # Dry run

Tailscale Service Hostnames

When migrating a service from indri to k8s, the Tailscale hostname must be freed:

1. Stop the service on indri
2. Clear the tailscale serve entry: ssh indri 'tailscale serve clear svc:<name>'
3. Delete the device from Tailscale admin console (user action required)
4. Deploy the k8s Ingress - it will claim the hostname

Use ssh indri 'tailscale serve status --json' to check current serve entries (the non-JSON output may be empty even when entries exist).

Third-Party Projects

When a task requires cloning or using a third-party git repository (e.g., for building from source), ask the user to mirror it on forge first, then clone from the mirror:

• Mirror location: https://forge.tail8d86e.ts.net/eblume/<project>.git
• Clone to: ~/code/3rd/<project>/

This avoids external dependencies and ensures the project is available even if the upstream is unreachable.

Task Discovery

To discover pending blumeops tasks, run:

mise run blumeops-tasks

This fetches tasks from the "Blumeops" project in Todoist (via 1Password for API credentials) and displays them sorted by priority: p1 (urgent), p2 (high), p4 (normal/default), p3 (backlog). The typical workflow is to pick a task from this list at the start of a session, then dive in with planning.

Credentials

The root store for credentials is 1password, which can be accessed via op --vault <vaultid> item get <itemid> --field fieldname --reveal, which will prompt the user for their assent and biometrics or password. Typically, use scripts to defer this action - try not to ever grab credentials directly. For instance, the indri.yml playbook starts with pre_tasks to gather the relevant secrets needed to provision its services. Some services have their credentials exported to files chmod 0600 on indri, but they still start out in 1password. In some cases you can test services with a command that grabs the credential, but try to use environment variables or other arrangements to avoid learning the credential yourself, and warn the user first.