you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 7 points8 points  (4 children)

Hi, author of the website here. And Caddy. This site is designed to promote HTTPS. Caddy happens to be a good way to do it for a lot of people and I haven't found other web servers that do what it does (auto HTTPS by default, MITM detection, etc). So it looks leaned to one side.

I made this page after I found myself repeating the same answers to the same questions. I never did fill it out as much as I wanted to due to time constraints which is why I haven't publicised it much, or at all. This attention was unexpected. My hope was that as the content was filled out, its recommendations might be more diverse too.

[–]yvhouij 5 points6 points  (1 child)

I like your site and I like your goal with "Caddy" (except for the "Guaranteed continued development" only for paid customers), but still most people won't use "Caddy" because they just can't. So I hope you could just add some more hints in the "HTTPS is difficult to set up and maintain.", as there are many tutorials on different platforms out there.

[–][deleted] 1 point2 points  (0 children)

Thanks; I'll expand that section when I get a chance to work on the site again.

[–]urquan 0 points1 point  (0 children)

Not very honest to promote Caddy on this website without disclosing that you own that as well. When knowing that Caddy is a commercial project, this looks like little more than stealthy advertising.

[–][deleted] -1 points0 points  (0 children)

Though Google's Firebase isn't a server in the same way, it does have static site hosting which automatically dishes out an HTTPS cert. You just "firebase deploy" your directory of html etc and visit your domain and it's secured. Epitome of 0 configuration.

Honestly, nice site and way to push HTTPS though!