Full stack local dev on Mac and Windows
Full stack developers on Mac and Windows run frontend and backend together in Rig: Vite or Next beside a Node API, Postgres or Redis sidecars, and queue workers from a Procfile or npm scripts — all in one project group with health-aware start order and a merged log stream. When the API fails with ECONNREFUSED on :5432, Rig shows which dependency is down and can reclaim stuck ports. Laravel shops pair Valet *.test with Vite, Horizon, and artisan sidecars in the same board. WordPress can sit beside Node the same day. MCP connects Cursor to live process health instead of guessing from pasted traces. Rig is not a container platform — it orchestrates native processes around Docker, Herd, or managed local Postgres when you need them, so the full stack boots as one named group instead of four terminals.
- Procfile / npm discovery for web, api, db, worker groups
- Health-aware start order and merged log stream
- Works with Vite/Next, Node APIs, Laravel sidecars, WordPress
- Native processes; Docker/Compose optional when needed
Can Rig run Vite and a Node API together?
Yes. Procfile and npm discovery boot web, api, db, and worker processes as a group with unified logs and per-process restart.
Does full stack local dev require Docker?
No. Many stacks run natively. Rig also supports Compose sidecars and managed local Postgres or Redis when your project needs them.