Show HN: Sonar – A tiny CLI to see and kill whatever's running on localhost

Re:Show HN: Sonar – A tiny CLI to see and kill whatever's ru... by msdz on Friday March 20, 2026 @05:49PM (#47461104)

> that they're unable to [manage and] kill child processes they themselves spawn makes it seem like they have zero clue about what they're doing.

Yeah, at the bare minimum these projects could also use something like portless[1] which literally maps ports to human- (and language model-)readable, named .localhost URLs. Which _should_ heavily alleviate assignment of processes to projects and vice versa, since at that point, hard-to-remember port numbers completely leave the equation. You could even imagine prefixing them if you've got that much going on for the ultimate "overview", like project1-db.localhost, project1-dev.localhost, etc.

[1] https://port1355.dev/

[ Parent | on HN ]

Re:Show HN: Sonar – A tiny CLI to see and kill whatever's ru... by embedding-shape on Saturday March 21, 2026 @06:50AM (#47465894)

Well, or just use port 0 like we've done for decades, read what port got used, then use that. No more port collisions ever. I thought most people were already aware of that by now, but judging from that project even existing, seems I was wrong.

[ Parent | on HN ]

Re:Show HN: Sonar – A tiny CLI to see and kill whatever's ru... by hackerthemonkey on Sunday March 22, 2026 @11:57AM (#47478837)

That’s a little different, right? Using port 0 would imply that clients have not hard coded what port they should connect to and also we don’t mind having duplicate processes occupying other ports which are no longer on active use

[ Parent | on HN ]