Doesn’t matter; we’ll map it to whatever the environment needs in the docker-compose.yaml.
All my homies use :3000
:3
Psh, we choose 443 and you know it! Just don’t ask me if we correctly enabled HTTPS…
I mean, if you’re serving over http, that is the port for it
Isn’t it port 80?
It’s both
We apparently could have been using 8008 this entire time for the same thing and we haven’t and I’m a little sour now.
9090
8888
Imagine using 8081 while 8080 is free. Truly criminal
I like 6969
4200 or 10420 too
Nice
That’s because 8080 is the official unprivileged alternative port for 80, the HTTP port. Web developers are usually using HTTP, so this makes perfect sense. If it supports HTTPS, then 8443, though that one isn’t official.
I run a few open source server projects, and they usually default to 8080 for this reason. I have one that uses 8888, and that’s only because it’s meant for temporary ad-hoc servers.
I’m working on an SFTP server, and it will use 2222, because that’s the most common unprivileged alternative port. There is no official alternative for SSH.