62 ms·
I love Caddy, using it as a Reverse proxy (even in docker) is so nice and easy. All you need is 2 lines of config: :2080 reverse_proxy :9000
by ttyyzz 3y ago
I love Caddy, using it as a Reverse proxy (even in docker) is so nice and easy. All you need is 2 lines of config:
:2080
reverse_proxy :9000
- dizhn 3y agoFree certs is also just a one line "email myemail@example.com". This applies to all sites and everything is auto managed. It also has a nice one line shortcut directive which applies to the vast majority of php sites out there.
- francislavoie 3y agoActually, you don't even need the email for certificate automation. You only need to give Caddy a valid public domain as your site address.
- dizhn 3y agoGreat. Either something changed, or I took something optional as required when I started using it. (Or perhaps one of the cert providers needs it while the other doesn't?) Good to know anyway. Cheers. Here's some older instructions for zerossl where email seems to be necessary. (https://caddy.community/t/using-zerossls-acme-endpoint/9406 https://caddy.community/t/using-zerossls-acme-endpoint/9406)
- ilyt 3y agoIf you just need that you don't really need reverse proxy in the first place...
- poorlyknit 3y agoThis way the app doesn't have to handle HTTPS though.
- ilyt 3y agoBut you have 2 apps running instead of one. There are already apps (and libs for them) to built-in the letsencrypt directly into the app. Sure if it is a 3rd party app, but if you're writing one just adding it to your app and simplifying everything around it is worth compared to adding additional component to deploy
- mholt 3y agoFor that you can even just use the command line without a file: $ caddy reverse-proxy --from :2080 --to :9000