oplkill@lemmy.world to memes@lemmy.worldEnglish · 2 months agoWhen webdevs choosing port for their applemmy.worldimagemessage-square52fedilinkarrow-up1452arrow-down17
arrow-up1445arrow-down1imageWhen webdevs choosing port for their applemmy.worldoplkill@lemmy.world to memes@lemmy.worldEnglish · 2 months agomessage-square52fedilink
minus-squareLucy :3@feddit.orglinkfedilinkarrow-up30·2 months agoUnix sockets all the way. The only open ports for web traffic should be the reverse proxy (so nginx).
minus-squarepassepartout@feddit.orglinkfedilinkarrow-up16·edit-22 months agoOr 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).
minus-squarehperrin@lemmy.calinkfedilinkEnglisharrow-up1·2 months agoHaproxy is great, but setup is hard. It’s more for load balancing than being an easy reverse proxy.
minus-squareMora@pawb.sociallinkfedilinkarrow-up1arrow-down2·edit-22 months agoSeeing that Red Hat also uses this in OpenShift: no. /s
minus-squarex00z@lemmy.worldlinkfedilinkEnglisharrow-up3·2 months agoI use docker ports but only allow the loopback like this: 127.0.0.1:11551:80 And then serve that app with the reverse proxy.
Unix sockets all the way. The only open ports for web traffic should be the reverse proxy (so nginx).
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).
Is haproxy okay?
haproxy is awesome
Haproxy is great, but setup is hard. It’s more for load balancing than being an easy reverse proxy.
Seeing that Red Hat also uses this in OpenShift: no. /s
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.