Journal
The Rig journal is first-hand notes from shipping a local-first control plane: why source stays on disk, how fleet start/stop works without a CI babysitter, why MCP is not a raw shell, and how teleport moves a working setup between machines. These are architecture notes, not keyword articles. Read them when you want the reasoning behind the product.
Section links
- Beta now, Pro later: an honest roadmap
- What running means on the board
- Morning after an OS update
- Docker Desktop vs Rig for local stacks
- Stop the share when the call ends
- Env profiles: client vs personal
- Local HTTPS without the cert dance
- The tray as a quiet control plane
- GitHub connect without folklore
- Crash diagnose in one bundle
- Team seats without a devops hire
- Why Live Link shares expire when the call ends
- Appearance that survives another Mac
- Procfile plus sidecars on one board
- Reclaim a port from the board
- Support vs community forum
- Cloud status page: your Mac is still fine
- What Rig does not replace
- Project-scoped MCP tokens
- The Continuity recovery key ritual
- Health checks that are not just curl
- Groups vs presets: which one you want
- WordPress local without Local WP drama
- Valet sites open from the board
- Mesh wake vs leaving the studio Mac on
- Soft Free quotas during beta: what they mean
- Ask Cursor to restart without kill -9
- When to stay local-only on purpose
- One log pane beats two laptops
- Sticky notes are not a control plane
- Morning boot without six tabs
- Backup the setup, not the repo
- Client preview without a staging box
- Port already in use: without lsof
- Scoped MCP, not a pasted terminal
- Herd is the runtime. Rig is the board.
- What is a local process control plane?
- Fleet control without a CI babysitter
- Why Rig keeps your code on the Mac
- MCP that isn't a raw shell
- Teleport a project between Macs