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...
[dead]
I Got Sick of Remembering Port Numbers
31–40 of 171 posts
Re: I Got Sick of Remembering Port Numbers
#32I think about a decade ago pow did something similar, but using the .test domain, and perhaps ruby specific
Re: I Got Sick of Remembering Port Numbers
#33What is the benefit of using HTTPS for this particular use case?
Some browser functions only work over https, localhost is the exception. So if you change localhost:5173 to myapp.vibe it needs a valid certificate.
Re: I Got Sick of Remembering Port Numbers
#34Earlier quoted context omitted.
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
this is a nice idea, but idk why, in macos if i do `nc -l 127.0.0.1 gopher` and then try to open url " http://127.0.0.1:gopher/ " - safari does not open it, no requests visible in the `nc` output. also `curl -v http://127.0.0.1:gopher/ ` gives error message * URL rejected: Port number was not a decimal number between 0 and 65535 * Closing connection curl: (3) URL rejected: Port number was not a decimal number between…
> http://...:gopher
is it http or gopher? :)
Re: I Got Sick of Remembering Port Numbers
#35I wonder why not use nginx and some local DNS settings to just serve all these local services under a new, local URL. Not too long ago I had a similar issue and solved with that.
I mean, that's essentially what he's recreating here it looks like
Re: I Got Sick of Remembering Port Numbers
#36Earlier quoted context omitted.
why?
VITE typed on a T9 keyboard is 8483.
T9 is predictive and based on a dictionary and training.
If you type "8483" on T9, your phone may offer "THUD" or "TITE" or all three, as choices.
But with a normal telephone keypad, if you dial, e.g. "(800) 555-VITE" then you will always dial "8483".
https://en.wikipedia.org/wiki/Phoneword
Also, a service port is always qualified by its protocol. There are separate port namespaces for each IP protocol that uses ports. "8483" is not a service port, until you spell it out:
8483/tcp
8483/udp
8483/sctp
8483/dccp
A TCP stream, for example, consists of a tuple:
src:port1 dst:port2Re: I Got Sick of Remembering Port Numbers
#37Aspire.dev should be mentioned here.
Re: I Got Sick of Remembering Port Numbers
#38What I do is use a hash function to derive port number from service name.
Re: I Got Sick of Remembering Port Numbers
#39Re: I Got Sick of Remembering Port Numbers
#40I use Cloudflare Tunnel so most of the products I build are exposed and listed there. I just add comments for those that aren't exposed (eg. browser extension dev port) to that file too. A single doc means coding agents know to look there and keep it updated too.