I Got Sick of Remembering Port Numbers
gregraiz.com
I Got Sick of Remembering Port Numbers
1–10 of 171 posts
Re: I Got Sick of Remembering Port Numbers
#2This project is essentially "give me some metadata & a command which takes env $PORT, and I'll handle the rest". Which is neat!
I am also sick of handling port numbers - I end up allocating them on a schema to different services, so for testing I can spool any VM/service combination and avoid crossover. But if I want the same service twice, ah...
It always fascinated me that ports don't have any kind of textual resolver, so you can bind to `:1234` and also say "please also accept `:foobar`". But that would itself require some kind of "port resolver" on a device, and that's another service to break and fix :)
Re: I Got Sick of Remembering Port Numbers
#3This project is essentially "give me some metadata & a command which takes env $PORT, and I'll handle the rest". Which is neat! I am also sick of handling port numbers - I end up allocating them on a schema to different services, so for testing I can spool any VM/service combination and avoid crossover. But if I want the same service twice, ah... It always fascinated me that ports don't have any kind of textual resol…
There is /etc/services to map port numbers to service names, and using getportbyname() to resolve port numbers.
Re: I Got Sick of Remembering Port Numbers
#4This project is essentially "give me some metadata & a command which takes env $PORT, and I'll handle the rest". Which is neat! I am also sick of handling port numbers - I end up allocating them on a schema to different services, so for testing I can spool any VM/service combination and avoid crossover. But if I want the same service twice, ah... It always fascinated me that ports don't have any kind of textual resol…
There is /etc/services to map port numbers to service names, and using getportbyname() to resolve port numbers.
DNS for /etc/hosts and now vibe.local for /etc/services. What will they think of next!
Re: I Got Sick of Remembering Port Numbers
#5Not the same, but omeone recently posted this "port" tool here on HN: https://github.com/raskrebs/sonar
Re: I Got Sick of Remembering Port Numbers
#6It's like someone should make a file... maybe in /etc ... and put short names for services in it... maybe it could be called /etc/services...
Re: I Got Sick of Remembering Port Numbers
#7It's like someone should make a file... maybe in /etc ... and put short names for services in it... maybe it could be called /etc/services...
And then they might code up some sort of service lookup tool thingy to use on the train wreck that is the modern web.
$ getent services gopher
gopher 70/tcpRe: I Got Sick of Remembering Port Numbers
#8I created something similar to help me spin up complex apps in multiple worktrees with full port orchestration: https://outport.dev/
Re: I Got Sick of Remembering Port Numbers
#9Bind to Port 0
Re: I Got Sick of Remembering Port Numbers
#10I've built this twice before. The main problem that I hit is that the AI agents suck at the process lifecycle management: leaving processes alive, starting the same daemon multiple times, etc.
From a brief glance over the code I like the approaches I see. Using the `/etc/resolver/` mechanism is a new trick to me!
The interesting part to me isn't the port numbers, it's the automatic service start/stop, including idle route shutdown.