Run & fix guides
Ports, databases, Compose, sessions, shortcuts.
38 guides in this category
- Ports, crashes, and reclaim: Who owns :3000, kill it safely, read crash exit codes.
- Managed Postgres and Redis: Spin up local DBs from Rig — host, user, pass, port.
- Docker Compose projects: Detect Compose stacks and run them from the control panel.
- Named sessions: Stop one context and start another without losing your place.
- Keyboard shortcuts: ⌘K palette and the hotkeys that matter day to day.
- Laravel, Valet, and PHP: Keep Valet on *.test; Rig runs queue, horizon, and logs.
- Lanes, env profiles, and worktrees: Local vs staging without melting .env files.
- rig CLI: run projects from the terminal: rig up, stop, lane — drive the Mac app from the terminal.
- Processes table: See every process Rig is managing for a project.
- Health-aware start order: Why Rig boots dependencies before your app.
- Project groups: Boot a whole stack with one action.
- Unified live logs: One stream for every process in the project.
- Filter and search logs: Cut noise when something 500s.
- Attention board: HTTP health, crash loops, ports, and deps that need eyes.
- Explain this error: Ask the agent assist to plain-English a log snippet.
- Git branch and status: See branch state beside the project you’re running.
- npm, pnpm, and bun: How Rig discovers and runs JS package scripts.
- Procfile projects: Classic multi-process apps without package.json scripts.
- Monorepos in Rig: One repo, many packages — how to structure projects.
- Restart vs stop: When to bounce a process instead of tearing it down.
- Native notifications: macOS alerts when Rig needs attention.
- Masked env manager: Edit lane env without flashing secrets on screen.
- Production lane caution: Treat production env like production access.
- Command palette (⌘K): Jump to projects and actions from the keyboard.
- Local HTTPS (.localhost): Trusted local HTTPS for projects that need it.
- Setup diagnose: Find missing tools and misconfig before you hunt logs.
- One-click fixes: Apply safe repairs Rig already knows how to do.
- Crash parse → suggest fix: How Rig turns exit codes into next steps.
- Git worktrees with lanes: Isolate checkouts for parallel features.
- Artisan sidecars: Queue, Horizon, schedule, Reverb as Rig processes.
- Composer and migrate one-shots: Run install / migrate without leaving Rig.
- Tail laravel.log: storage/logs without hunting the filesystem.
- Open Valet *.test site: Jump to the local Valet URL Rig detected.
- WordPress local sites: One-click create plus detection of existing WP folders.
- Common port conflicts: 3000, 5173, 8080 and friends.
- When Docker Desktop is required: Managed databases need a container engine.
- Freelancer / agency tips: Client lanes without melting your day job env.
- Morning boot checklist: Get the day’s stack up without heroics.
See all Rig documentation in the knowledge base.
Related
Section links
- Ports, crashes, and reclaim
- Managed Postgres and Redis
- Docker Compose projects
- Named sessions
- Keyboard shortcuts
- Laravel, Valet, and PHP
- Lanes, env profiles, and worktrees
- rig CLI: run projects from the terminal
- Processes table
- Health-aware start order
- Project groups
- Unified live logs
- Filter and search logs
- Attention board
- Explain this error
- Git branch and status
- npm, pnpm, and bun
- Procfile projects
- Monorepos in Rig
- Restart vs stop
- Native notifications
- Masked env manager
- Production lane caution
- Command palette (⌘K)
- Local HTTPS (.localhost)
- Setup diagnose
- One-click fixes
- Crash parse → suggest fix
- Git worktrees with lanes
- Artisan sidecars
- Composer and migrate one-shots
- Tail laravel.log
- Open Valet *.test site
- WordPress local sites
- Common port conflicts
- When Docker Desktop is required
- Freelancer / agency tips
- Morning boot checklist