Lexicanum
Notes and references on the stuff I actually run. Each entry is a deep-dive: implementation steps, real configs, the failure modes I hit along the way. Guides are task-sequenced how-tos; reference docs explain how a system works and which option to pick. / searches everything.
Supabase and Postgres
Tenancy, migrations, auth, network access, the database and the platform services, mostly measured on throwaway projects.
All Supabase and Postgres docs (68)
- A backend-for-frontend fan-out on Supabase Edge Functions
- Build a public-record entity graph on managed Postgres
- Consolidating one Supabase project per customer onto a shared project
- Detach a Supabase branch from its git branch without deleting it
- Measure a Postgres change with pg-analyser bench
- Migrate a Supabase project to another region, end to end
- Migrating a static MongoDB archive into Postgres with the Supabase MongoDB wrapper
- Monitor Supabase with Grafana: dashboards and alerting
- Moving Supabase projects under one organization
- Per-project cost attribution on Supabase
- Promoting a tenant to its own Supabase project
- Put an IAP over the Supabase Data API
- Query Supabase project logs through the Management API after logs.all
- Run your own PostgREST against a Supabase project
- Running a platform on the Supabase Management API
- Running many tenants on one Supabase project
- Set up AWS PrivateLink to Supabase with OpenTofu
- Supabase preview-branch compute sizing & a CI parity model
- Supabase resilience runbook: probes, TTL levers, edge cache, warm standby
- Trusted-device MFA and impersonation audit trails on Supabase Auth
- Upgrade a Supabase project to a new Postgres major version, end to end
- @supabase/server auth modes on Edge Functions and WorkersREFERENCE
- AWS PrivateLink to Supabase: an architecture referenceREFERENCE
- CipherStash on Supabase: EQL grants, the supabase-js wrapper and ZeroKMSREFERENCE
- Cloudflare Workers + Supabase: an architecture referenceREFERENCE
- Entity graphs on managed PostgresREFERENCE
- Foreign keys to auth.users block sign-in during validationREFERENCE
- Migrating PBKDF2 password hashes into Supabase AuthREFERENCE
- Multigres OSS failover: what a client seesREFERENCE
- One envelope-encrypted app on managed and self-hosted SupabaseREFERENCE
- One Supabase project per tenant or many tenants per projectREFERENCE
- OrioleDB on Supabase: what hosted projects do differentlyREFERENCE
- pg_cron on Supabase across restarts and resizesREFERENCE
- pg_net on Supabase under loadREFERENCE
- pgjdbc and HikariCP on Supabase connection pathsREFERENCE
- pgmig, logical-replication migration scope and gatesREFERENCE
- Postgres full-text search: ranking only what the rare words matchREFERENCE
- Restricting access to a Supabase projectREFERENCE
- RLS policy cost on SupabaseREFERENCE
- RLS without Supabase Auth: JWT claims over the wireREFERENCE
- Self-hosted Supabase Docker defaults in 2026REFERENCE
- Static site hosting on SupabaseREFERENCE
- Stripe Sync Engine: schema projection, version drift, and the FDW alternativeREFERENCE
- Supabase Auth end to endREFERENCE
- Supabase Auth providers: custom OIDC, passkeys, SAML and a sign-in canaryREFERENCE
- Supabase CLI 2.120.0: pg-delta vs migra, config pull and the no-Docker stackREFERENCE
- Supabase compute and disk sizingREFERENCE
- Supabase Data API connection pool and capacityREFERENCE
- Supabase data residency and sovereigntyREFERENCE
- Supabase disaster recovery tiers: daily backups, PITR, warm standby - RPO, RTO, and costREFERENCE
- Supabase Edge Function limitsREFERENCE
- Supabase incident classes and client workaroundsREFERENCE
- Supabase log volume per requestREFERENCE
- Supabase observability surface: trace headers, health advisors, log sourcesREFERENCE
- Supabase Pipelines (public alpha): what a PAT reaches and how the engine replicatesREFERENCE
- Supabase read replicas: how requests reach them and what they costREFERENCE
- Supabase Realtime: filters, disconnect loss, Broadcast Replay and binaryREFERENCE
- Supabase Storage image transformations: billing, runtime behaviour, and the abuse surfaceREFERENCE
- Supabase Storage large objects: multipart, ranges, conditionals, CDN and TUSREFERENCE
- Supabase Storage surface: direct SQL deletes, list pagination, S3 key handlingREFERENCE
- Temporary token-based database access (JIT): grants, expiry and what gets loggedREFERENCE
- Turso, D1, Durable Objects and Supabase Postgres from one Cloudflare WorkerREFERENCE
- Two Supabase projects on one GitHub repositoryREFERENCE
- WAL on object storage: OrioleDB's S3 mode against Turso CloudREFERENCE
- What a Supabase platform operation costs a clientREFERENCE
- What an unchanged upsert costs in PostgresREFERENCE
- What deleting a wrapper in the Supabase Dashboard dropsREFERENCE
- Where Supabase audit events are stored and who can delete themREFERENCE
Cloudflare
Workers, caching, tunnels, Access and Magic WAN.
All Cloudflare docs (9)
- Extending your Terraform configuration with the http provider
- GitHub Actions with Cloudflare
- Magic WAN and its interoperability
- Securing kubectl with Cloudflare Access for SaaS
- Setting up Cloudflare Tunnel on Google Cloud Run
- Caching with Cloudflare Workers: when to use whatREFERENCE
- Gatekeeper IAM GatewayREFERENCE
- Media transformation architectureREFERENCE
- We have fraud detection at homeREFERENCE
Kubernetes
k3s on ARM64: deployment, ingress, and observability.
Networking and DNS
The NixOS edge router, the switch, Caddy, and the resolvers and authoritative DNS behind them.
All Networking and DNS docs (8)
- Caddy reverse proxy with Coraza WAF and management dashboard
- Glory-Hole DoT DNS service interop with Magic WAN and VyOS
- Recursive DNS on GL-MT3000: Unbound behind AdGuard Home
- Running OpenWrt on a XikeStor SKS8300 switch
- Edge Caddy as a native NixOS serviceREFERENCE
- knotea, a resolver and authoritative DNS server in one binaryREFERENCE
- NixOS edge router network designREFERENCE
- Running a domain that does not link back to youREFERENCE
Homelab
Storage and backups, the hosts and how they are deployed, the services they run, and the home sensors.
All Homelab docs (32)
- Add Prometheus monitoring to a Compose Postgres stack
- AirGradient ONE on ESPHome, fully local
- Blind playback-rate listening test
- Docker networking patterns for the arr stack
- Migrating a NAS with migctl
- Moving an ESPHome fleet to a new SSID
- Multi-site Vaultwarden: PostgreSQL, R2 sync, and Cloudflare load balancer failover
- Running a bridged access point on mainline OpenWrt
- Self-hosting Matrix + Element Call on k3s with Cloudflare and VyOS
- Singapore weather alerts and live maps with Home Assistant and Grafana
- slskd behind WireGuard VPN with port-forward sync
- A self-hosted web research stack for coding agentsREFERENCE
- Composer: a GitOps control plane for Docker Compose stacksREFERENCE
- Declarative backups on a ZFS homelab: nix timers, sanoid, syncoidREFERENCE
- Designing glanceable dashboards for home environmental telemetryREFERENCE
- Docker Servarr stack security: hardening media automationREFERENCE
- drawbridge, an mTLS proxy for the Docker socketREFERENCE
- End-to-end encrypted push notifications through an untrusted brokerREFERENCE
- Home IoT: an ESPHome fleet on a Flint-bridged VLANREFERENCE
- Isolating CI Docker storage on a gateway after a DHCP outageREFERENCE
- Lockstep: watch-party sync for JellyfinREFERENCE
- Monitoring a self-hosted stack behind a policy-drop edgeREFERENCE
- OpenAQ community PM2.5 in Home AssistantREFERENCE
- Placing app state on NVMe or HDD in a ZFS homelabREFERENCE
- Replacing a paid search API with a self-hosted pipelineREFERENCE
- Sharing one NAS GPU between chat, embeddings, a writer model and photo MLREFERENCE
- slskarr: one process for Soulseek, the PIA tunnel, and the Lidarr importREFERENCE
- Synchronized playback with far-away viewersREFERENCE
- Tailscale homelab reference: overlay as second path and management planeREFERENCE
- Three NixOS hosts, one deploy interfaceREFERENCE
- Why UCI SSIDs disappear from a Flint 2 after rebootREFERENCE
- ZFS dataset mounts on NixOSREFERENCE
Forge and CI
The self-hosted Forgejo forge: repositories, Actions runners, releases, and the deploys they trigger.
All Forge and CI docs (12)
- Building Windows releases on a Linux-only Forgejo runner
- Forgejo recovery runbooks
- Migrating a repo fleet from GitHub-primary to Forgejo-primary
- Porting a GitHub Actions workflow to Forgejo Actions
- Wiring a Forgejo push to a Composer GitOps deploy
- Carrying patches on a fork: layout, drift checks and rebase gatesREFERENCE
- Forgejo as the primary forge on the NixOS edge routerREFERENCE
- Forgejo storage, backups and cachesREFERENCE
- Releases and the registry decision on a self-hosted ForgejoREFERENCE
- Self-hosted Renovate for a Forgejo-primary Docker Compose fleetREFERENCE
- The Forgejo Actions runner: build and lifecycleREFERENCE
- Vigil fleet vulnerability sweep, exploitability enrichment, and CI gatingREFERENCE
Secrets
Where credentials live, how they are encrypted, rotated, and kept out of agent transcripts.
All Secrets docs (7)
- Building and checking a secretctl registry
- Encrypting Docker Compose .env files with SOPS and age
- Rotating a credential end to end with secretctl
- Unlocking rbw with a YubiKey touch on Linux and WSL2
- Choosing a secrets backend: SOPS+age, Vaultwarden, OpenBao, and InfisicalREFERENCE
- Keeping credentials out of coding-agent transcriptsREFERENCE
- secretctl: stores, digests and commandsREFERENCE
Hardware design
The GRIDDLE LX Hall-effect keyboard: PCB, case, firmware and ordering, plus QMK keymaps.
All Hardware design docs (7)
- Creating QMK, VIA, and Vial keymaps
- Designing the GRIDDLE LX keyboard case in build123d
- Ordering a 4-layer keyboard PCBA and plate at JLCPCB
- Porting a QMK keymap to a libhmk keyboard.json
- Generating and checking the GRIDDLE LX PCB from codeREFERENCE
- GRIDDLE LX: a 5x12 Hall-effect keyboardREFERENCE
- Keyboard typing height: standards, the case stack and keycap profilesREFERENCE
Reverse engineering
Locked microcontrollers, fault injection, side channels and decompilers.
All Reverse engineering docs (7)
- CH32V305 WCH-LinkE read-only debug triage
- Patching Pulsar X2 CrazyLight Mini firmware
- Read-only SWD and voltage-glitch harness on a locked Nuvoton M483
- Test a firmware cipher with power side-channel analysis on Cortex-M
- Nuvoton M483 flash locks and fault-injection readbackREFERENCE
- Reverse engineering with a coding agent and headless GhidraREFERENCE
- When blurred or pixelated text can be recoveredREFERENCE
Agents and LLMs
The agent harness, the models behind it, and how agent work is reviewed.
All Agents and LLMs docs (26)
- Auditing which OpenRouter provider served your agent's requests
- Diagnosing a reasoning cliff in an agentic model
- Leak gates that let coding agents push without approval prompts
- A cross-client memory store for coding agentsREFERENCE
- A kanban board for coding agentsREFERENCE
- A personal knowledge graph with a local LLMREFERENCE
- A self-hosted transcription service for coding agentsREFERENCE
- A sensor-gated coding-agent loop compared with 2026 harnessesREFERENCE
- A skills system for coding agentsREFERENCE
- Agent image generation and LoRA trainingREFERENCE
- Benchmarking local models for agent workREFERENCE
- Context, prompt cache, and compaction in a coding-agent harnessREFERENCE
- Documentation over SSH for coding agentsREFERENCE
- Guard extensions that enforce prose and process rules in a coding agentREFERENCE
- History of the pi coding-agent harnessREFERENCE
- How this site is writtenREFERENCE
- Labelling AI use with the 0rwx frameworkREFERENCE
- Model routing in a coding-agent harnessREFERENCE
- Qwen3.8-27B for agentic work: speculative decoding and reasoning effortREFERENCE
- Resuming any coding-agent session from any directoryREFERENCE
- Reviewing an infrastructure change with three model familiesREFERENCE
- Running agent git commands without per-command approval promptsREFERENCE
- Scheduling one GPU between LLM, image and training workREFERENCE
- Sharing guards and tools between two coding-agent harnessesREFERENCE
- Subagents, worktrees, and parallel agent workREFERENCE
- Testing the assumption a plan depends on before building itREFERENCE
Workstations
Windows, WSL2 and Steam Deck setup, latency measurements, and graphics, film and site design.
All Workstations docs (19)
- Fixing merged reports from an 8 kHz mouse on Windows
- Keeping /run/user alive across Docker Desktop stops on WSL2
- Keeping Windows SMB credentials in sync with a sops-managed NixOS Samba server
- Making cliamp play sound on WSL2
- Measuring HDMI audio and USB DAC output latency on Windows
- Measuring USB audio output latency on Windows with a loopback cable
- Reclaiming disk space from WSL2 and Docker Desktop
- Removing a stuck WinFsp or rclone drive letter on Windows
- Setting up Steam Deck (Steam OS) with Nix
- Tuning a 10GbE link end to end
- apm, an APM counter that adds no input latencyREFERENCE
- Declarative media player configs: VLC and MPC-HCREFERENCE
- Diagnosing Windows mapped drive letters that will not openREFERENCE
- GPU voltage-frequency curve control without AfterburnerREFERENCE
- Linear Film Negative Inversion & Develop PipelineREFERENCE
- One design language for a photo site and self-hosted toolsREFERENCE
- Print-ready graphics: what a printer needs from your logoREFERENCE
- Replacing a desktop utility with a zero-wakeup capture daemonREFERENCE
- Typography and layout for this docs siteREFERENCE