I Got Sick of Remembering Port Numbers • Hacker News Board

Re: I Got Sick of Remembering Port Numbers

#11

Post by TomK32 » Fri, May 01, 2026, 4:23 AM UTC

zdw wrote: post #6

It'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...

Sure, but they are running web-apps they've vibe-coded (hence the .vibe tld) and for that use-case of many web apps that I run in docker containers I use nginx-proxy [0]. All the container needs is a VIRTUAL_HOST environment variable with the domain and what my router needs is an address entry for the wildcard subdomains. I even have nginx-proxy on a internet-accessible staging server.

[0] https://github.com/nginx-proxy/nginx-proxy

Re: I Got Sick of Remembering Port Numbers

#12

Post by miyuru » Fri, May 01, 2026, 4:24 AM UTC

axus wrote: post #4

winstonwinston wrote: post #3

Earlier quoted context omitted.

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!

SVCB DNS records

Re: I Got Sick of Remembering Port Numbers

#13

Post by elchief » Fri, May 01, 2026, 4:27 AM UTC

I'm slightly annoyed that vite's default port isn't 8483

Re: I Got Sick of Remembering Port Numbers

#14

Post by thunderbong » Fri, May 01, 2026, 4:27 AM UTC

kasperni wrote: post #5

Not the same, but omeone recently posted this "port" tool here on HN: https://github.com/raskrebs/sonar

HN Thread

https://news.ycombinator.com/item?id=47452515

Re: I Got Sick of Remembering Port Numbers

#15

Post by chrisweekly » Fri, May 01, 2026, 4:27 AM UTC

elchief wrote: post #13

I'm slightly annoyed that vite's default port isn't 8483

why?

Re: I Got Sick of Remembering Port Numbers

#16

Post by nektro » Fri, May 01, 2026, 4:28 AM UTC

i have something like this too, currently a 60 line nodejs file

Re: I Got Sick of Remembering Port Numbers

#17

Post by arjie » Fri, May 01, 2026, 4:34 AM UTC

This is a valid concern, certainly. I use kube for most things so it's not a problem, but my homeserver and its apps run on quadlets that I manage. In my case, I just added a README.md in the server account folder that each project's CLAUDE.md or whatever is configured to read. Then it selects a port and sticks that in the document and to be honest I have a few tens of services and it works. Haha, a direct replacement of machine for my own process.

Re: I Got Sick of Remembering Port Numbers

#18

Post by kseistrup » Fri, May 01, 2026, 4:38 AM UTC

chrisweekly wrote: post #15

elchief wrote: post #13

I'm slightly annoyed that vite's default port isn't 8483

why?

VITE typed on a T9 keyboard is 8483.

Re: I Got Sick of Remembering Port Numbers

#19

Post by [deleted] » Fri, May 01, 2026, 4:39 AM UTC

[deleted]

Re: I Got Sick of Remembering Port Numbers

#20

Post by otabdeveloper4 » Fri, May 01, 2026, 4:39 AM UTC

tolciho wrote: post #7

zdw wrote: post #6

It'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/tcp

Heck, maybe even `resolvectl service`?