New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch to Caddy on Docker #1132
Comments
@jayfk, I've heard "rumours" (yeah, sort of "some people say"-stuff) that Caddy is not yet ready for wide real-world adoptioin, or I am wrong? |
I've been using Caddy for a lot of smaller and mid-sized sites and I'm really happy with it. Djangopackages.org runs Caddy for ~6 months, no problems. I wouldn't use it for very large sites, but the only reason is that nginx Plus offers some great enterprise features. |
@jayfk, what do you think about introducing a separate 'nginx-master' branch off of |
@jayfk, even better: We could introduce these two mutually-exclusive cookiecutter-django template options, and stick with one branch. |
I'm -1 on that. Supporting multiple servers is a huge pain in the long run. Either Caddy or nginx. I'm in huge favor of Caddy. It's simple, has a great config file format, supports Lets Encrypt with secure defaults out of the box and it's super easy to add basic load balancing capabilities. A prereq for #1133. @pydanny @audreyr @luzfcb @burhan @theskumar @webyneter and everyone interested. Can I get a vote on that? 👍 for caddy, 👎 against it. |
@jayfk , I trust your experience wholeheartedly on this 😄. |
@jayfk, how is this going? Can I be of any help? |
Just for reference, I don't think caddy works on AWS when using and AWS Cert and load balancer. Here's a related article. https://msaizar.com/blog/cookiecutter-django-nginx-route-53-and-elb/ |
Caddy is so much easier to set up using let's encrypt than nginx. A perfect fit for Cookiecutter Django.
The text was updated successfully, but these errors were encountered: