Introducing Lewp

For anyone who has worked locally on multiple applications, you quickly learn that port conflicts become a nuisance. Rails, as an example, defaults to port 3000. This means every time you run bin/dev or rails server, you need to remember or configure a different port. On teams, you then need to distribute and standardize those overrides.Then what happens when your application needs more than one port? Using Inertia.js, for example, you may also have a Vite server running behind the scenes, which needs a different port of its own. Add PostgreSQL, Redis, or another service, and a single checkout can depend on several ports.And of course, now that coding agents want to spin up multiple worktrees, this problem gets even more complicated. Even with the standard configuration you might have made as a team to isolate your projects, you run into conflicts again because every checkout is still part of the same project and starts with the same defaults.There are a couple of other solutions out…