When webdevs choosing port for their app
-
This post did not contain any content.
-
This post did not contain any content.
Unix sockets all the way. The only open ports for web traffic should be the reverse proxy (so nginx).
-
Unix sockets all the way. The only open ports for web traffic should be the reverse proxy (so nginx).
wrote last edited by [email protected]Or Caddy (simpler than and imho spiritual successor to nginx).
Or Traefik (has loads of convenient middlewares for reverse proxy stuff).
Or Apache (if it is somehow better suited to your use case).
-
Unix sockets all the way. The only open ports for web traffic should be the reverse proxy (so nginx).
Is haproxy okay?
-
This post did not contain any content.
Psh, we choose 443 and you know it! Just don’t ask me if we correctly enabled HTTPS…
-
This post did not contain any content.
Imagine using 8081 while 8080 is free. Truly criminal
-
This post did not contain any content.
Me: 5000 it is.
-
This post did not contain any content.
Doesn't matter; we'll map it to whatever the environment needs in the docker-compose.yaml.
-
This post did not contain any content.
All my homies use :3000
-
Me: 5000 it is.
Arg, my Synology servers are down. Thanks.
-
Psh, we choose 443 and you know it! Just don’t ask me if we correctly enabled HTTPS…
Back in the day I home hosted shit using http over 443 because my ISP blocked 80 inbound but not 443. It was a little weird but it worked lmao.
-
Back in the day I home hosted shit using http over 443 because my ISP blocked 80 inbound but not 443. It was a little weird but it worked lmao.
I run ssh over 443 because every network out there seems to block non-http ports.
-
Unix sockets all the way. The only open ports for web traffic should be the reverse proxy (so nginx).
I use docker ports but only allow the loopback like this:
127.0.0.1:11551:80And then serve that app with the reverse proxy.
-
This post did not contain any content.wrote last edited by [email protected]
adds a one to it
next app...
ports: - 8081:8081Ughhhhh
-
This post did not contain any content.
9090
8888
-
This post did not contain any content.
go2rtc, a camera streaming tool that's useful for security cameras, at least has some humor in their choice --- port 1984, of course.
-
This post did not contain any content.
Call me crazy, but I like default ports to look like default ports. If I want it to stick around, I’ll pick a port on my own.
-
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.
-
Is haproxy okay?
wrote last edited by [email protected]Seeing that Red Hat also uses this in OpenShift: no. ~/s~
-
This post did not contain any content.
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.
