Proactive port conflict scan
-
Right now Rig only tells you who owns a port reactively, when a start fails on bind. Add a read-only scan that shows what's already listening on common dev ports (and on the ports your added projects declare) before you hit start, so conflicts are visible upfront instead of discovered by a failed boot. Not full system auto-discovery — just extending the existing "who owns this port" lookup to run proactively across a range rather than waiting for EADDRINUSE.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login