You must log in or register to comment.
go2rtc, a camera streaming tool that’s useful for security cameras, at least has some humor in their choice — port 1984, of course.
Okay, that’s pretty good.
Whatever dev came up with that was probably very proud.
adds a one to it
next app…
ports: - 8081:8081Ughhhhh
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.
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.
Me & the boys serving http on the boob port
I prefer the secure version, boobs.
As long as it is configurable, ideally via env, I dont care about the port.
This could be important for restricted Kubernetes clusters (or certain Gluetun configs). Don’t be Nextcloud with their default port of 80 in their Apache image with only hacky ways to change that. God, I hate Nextcloud. They are truly becoming the next Wordpress.
I like 6969
All my homies use :3000
:3
Doesn’t matter; we’ll map it to whatever the environment needs in the docker-compose.yaml.
50501?
