this post was submitted on 19 Jul 2023
405 points (96.3% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54411 readers
205 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
 |
 |
|---|---|
| Ko-fi | Liberapay |
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Caddy in a docker container took me about 5 minutes to setup. Reverse proxying is a one-liner in Caddy
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.
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.
Okay this is neat, but still:
First OP needs to configure his DNS service.
Then he needs to port forward 443 (if I'm reading the instructions correctly).
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.