[johnnycarcin]

Couldn't agree more. I love tinkering around with things and building setups just to learn, but for something like a personal webpage I just want simple.

I use hugo and then setup my output folder (where the generated output goes) as a git repo. Generate the site -> git commit/push -> Caddy. Caddy has a feature to pull in content from a git repo so when you couple that with the built-in Let's Encrypt support it makes it dead simple.

[bovermyer]

I also use hugo. In my setup, though, I have everything in one git repo - config files, content files, theme, output, etc. Nginx exposes its output directory.

I stopped using Caddy when I discovered that it didn't support one of the unusual TLDs I had. Maybe I should give it another go, though. That was over a year ago.

[StavrosK]

What do you mean it didn't support a TLD? It's a server, how does it need to "support" TLDs? In my experience, you just specify the hostname and it works.

[bovermyer]

I'm not sure. All I know is that when I had a domain name in there ending in ".space," the server ignored that config and served everything else.

I assumed it was because of the TLD, because everything else was otherwise identical to some of the other virtualhosts.

[StavrosK]

Huh, that's really odd. I wonder if it's a regex gone wrong.

[mholt]

Really? That shouldn't be the case: Caddy doesn't care about TLD. Will you file an issue?