oplkill@lemmy.world to memes@lemmy.worldEnglish · 12 days agoWhen webdevs choosing port for their applemmy.worldimagemessage-square34fedilinkarrow-up1391arrow-down17
arrow-up1384arrow-down1imageWhen webdevs choosing port for their applemmy.worldoplkill@lemmy.world to memes@lemmy.worldEnglish · 12 days agomessage-square34fedilink
minus-squareLucy :3@feddit.orglinkfedilinkarrow-up26·12 days agoUnix sockets all the way. The only open ports for web traffic should be the reverse proxy (so nginx).
minus-squarepassepartout@feddit.orglinkfedilinkarrow-up14·edit-212 days 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·10 days agoHaproxy is great, but setup is hard. It’s more for load balancing than being an easy reverse proxy.
minus-squarex00z@lemmy.worldlinkfedilinkEnglisharrow-up3·12 days 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.
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.