I think it was five minutes for you because you're already well acquainted with the concepts and/or tool. These are some older instructions for setting up Caddy and it's not just minutes of work for the average person. The certificate part alone would take more than five minutes, and HTTPS is a must for a smooth experience for users.

[–] entropicdrift@lemmy.sdf.org 1 points 1 year ago* (last edited 1 year ago) (1 children)

That's for Caddy 1.1

In Caddy 2 and higher it handles the cert stuff automatically with Let'sEncrypt.

Actually, looking in that guide you linked, the change to add https is a very small change in the config file as well. Perhaps you mean doing port forwarding in the router or setting up a domain/DNS is difficult? But those parts have nothing to do with Caddy itself.

Try looking at an equivalent guide for its competitors Nginx or Traefik. They're far more complex to get set up.

[–] JasSmith@kbin.social 1 points 1 year ago (1 children)

Okay this is neat, but still:

If you use any other domain name, Caddy will attempt to get a publicly-trusted certificate; make sure your DNS records point to your machine and that ports 80 and 443 are open to the public and directed toward Caddy.

First OP needs to configure his DNS service.

Then he needs to port forward 443 (if I'm reading the instructions correctly).

[–] entropicdrift@lemmy.sdf.org 1 points 1 year ago

For sure, Caddy's the easiest tool I've found for this part of the chain.

DNS stuff is somewhat easy if you get a good provider, but it depends on a couple things. Port forwarding generally is a pain in the ass.