4 ms·
I just keep using HAProxy for doing the plumbing and keeping app side as simple as possible (which is often just "a web server builtin into app" + maybe static
by ilyt 3y ago
I just keep using HAProxy for doing the plumbing and keeping app side as simple as possible (which is often just "a web server builtin into app" + maybe static serving nginx if app is in slow language that can't handle serving statics quickly)
But automatic https does look convenient, no need to have separate certbot running
- melx 3y agoHAProxy 2.8 has improved[0] Let's Encrypt integration by using acme.sh (so you can get rid of certbot). It still needs a cron job/systemd timers to do renewal of certs but acme.sh is just bash script so you don't need (extra?) system deps for installing it, while certbot requires Python and 12 python libs on my system (Fedora). And nowadays the "recommended" way to get certbot is via Snap (package manager)... [0] https://www.haproxy.com/blog/haproxy-and-let-s-encrypt https://www.haproxy.com/blog/haproxy-and-let-s-encrypt
- anakaine 3y agoWe use Caddy in production. The driving force for change was built in automatic https. It just simply works.
- mholt 3y agoI'm happy to hear this -- we work hard on our auto-HTTPS features!
- eyegor 3y agoHaproxy is great in the end but it is pretty awful to work with. Once you've toiled in the mines of acl commands, going back to nginx/caddy is a breath of fresh air. Unless recent versions have completely changed the game, using haproxy when you don't have to is a massive time waster.