It’s also nice because it has ACME built right in (it takes care of your SSL/TLS certs for your site automatically without setting up a cron job or certbot yourself)
I hate the non-static world of the web as it exists today, so I just pre-gen static HTML pages and serve them direct from Caddy; or reverse proxy some other service that's running its own delivery method. Jellyfin, Sonarr, Radarr, etc -- none of them need a "proper" web server running in front of them.
Yeah steep is putting it mildly, it's not worth it below a certain scale. What it excels at is highly dynamic environments where things get spun up and down on the regular and all with auto scaling.
What's wrong with caddie? Not in the loop
Nothing wrong with caddy, in fact they released a pretty nice update 2.8 just recently.
Then why does the meme depict users leaving?
You think some rando on the internet making linux memes for upvotes is a good source of factual truth?
No, but I'm trying to get the meme
It’s the age-old choice between old and stable vs new and shiny.
The meme’s opinion is that old stable is the better choice, although that’s not always true.
What's
wrong withcaddie? Not in the loopA reverse proxy and web server that is easy to configure
It’s also nice because it has ACME built right in (it takes care of your SSL/TLS certs for your site automatically without setting up a cron job or certbot yourself)
ty
: ( probably nothing, I just don't understand the instructions well enough yet ( last I tried to read them)
wishing I could get the caddy local duckdns setup for vaultwarden going
I'm dealing with almost the same problem!
I hate the non-static world of the web as it exists today, so I just pre-gen static HTML pages and serve them direct from Caddy; or reverse proxy some other service that's running its own delivery method. Jellyfin, Sonarr, Radarr, etc -- none of them need a "proper" web server running in front of them.
I'll stick with Caddy
Caddy is amazing and actually simple.
caddy-docker-proxy is amazing, I just ned to specify two labels in the compose file and the service is online via a reverse proxy and automatic ssl.
I do it the hard way with my internal DNS and DHCP Server and lxc containers.
Caddy has been the easiest reverse proxy I've setup over the years.
I used it when I was running my server on windows but now I use nginx proxy manager it doesn’t get easier than that.
Npm is nice for having a GUI but once you need something more advanced it sucks imo. I had a lot of trouble with it's TLC certificates too.
Did you mean Sozu instead of "Suzu"? I can't find anything in "Suzu"
Ah my fault, that's correct
Love me some Traefik
Either I am too stupid for Traefik or it is needlessly complicated (or both). Their docs didn't help either, this image was relatable.
Traefik is love. Traefik is life. How could you say "no" to that mascot!?
Weird, isn't it. A lot of those successful services have cute little mascots. It influences me more than it should.
Your comment reminded me of this https://pixelastic.github.io/pokemonorbigdata/
If it's so well known, the configuration should be trivial ;)
Envoy proxy gang
I would love to learn Envoy but it looks like a truly steep curve.
Yeah steep is putting it mildly, it's not worth it below a certain scale. What it excels at is highly dynamic environments where things get spun up and down on the regular and all with auto scaling.
There are servers but nginx?