I'll concede there's probably a little more hands on work doing things this way, but I do like having a good grip on how things are working rather than leaning on a convenient tool. Maybe you could convince me Sidekick has more advantages?
I'll concede there's probably a little more hands on work doing things this way, but I do like having a good grip on how things are working rather than leaning on a convenient tool. Maybe you could convince me Sidekick has more advantages?
It's always a balancing act between outsourcing your heavy lifting, and having to trust that party and depend on them.
I think the benefits of Cloudflares DoS protection are vastly oversold and absolutely unnecessary for 99% of businesses.
(I think the false positives where some users randomly get captchas are actually bad for business)
Even though I agree with you in spirit. The chances that you will need it are slim.
I'd also not want to have cloudflare as an extra company to trust, point of failure and configuration to manage.
But isn't this a little too tied to Cloudflare?
Caddy as a reverse proxy on that VPS would also give us free HTTPS. The downside is less security because no CF tunneling.
1. nginx + letsencrypt
2. forward based on host + path to the appropriate local docker
3. run each thing in the docker container
4. put Cloudflare in front in proxy DNS mode and with caching enabled
Your thing is obviously better! Thank you.
How do you run the containers on your VPS tho? You could still use Sidekick for that!
I think your setup is one step up in security from Sidekick nonetheless. A lot more work it seems too