3 ms·
We've had great fun with Caddy for Version 1 of our custom domains feature. For Version 2, we've done a lot of work with Matt and the solution we've now reache
by JackWritesCode 6y ago
We've had great fun with Caddy for Version 1 of our custom domains feature.
For Version 2, we've done a lot of work with Matt and the solution we've now reached is:
1. DynamoDB as storage for certificates, allowing sharing between servers without regenerating during an issue with an availability zone
2. Multiple Caddy reverse proxy servers in different regions
3. AWS Global Accelerator to route the user to the closet server to them
It's so great because we can also proxy our CDN through Caddy (yes, it needs to go through the user's custom domain), and we've got insanely fast response times on that.
We've load tested the proxy servers and they can handle an incredible amount, we're very pleased with the solution.
I will be publishing and sharing an article soon, detailing my journey and our final solution.
- going_to_800 6y agoLove this! I'm really REALLY interested in this post because I'm facing the same issue and TBH I'm not that great with servers myself.