[diakritikal]

Just using caddy server seems a lot simpler...

[qrv3w]

+1 for Caddy. I was using NGINX a long time, and wrote some similar scripts to make certificates for my web apps. After I switched to Caddy I had a 6x smaller config file, no more ln -s, and HTTPS without every having to think about it!

[tlrobinson]

Neat, I like that when started with no arguments/config it just serves the files in the current directory, but then you can customize it from there.

I have "alias webserver='python -m SimpleHTTPServer'" in my shell config, but I think I'll switch to Caddy.

[callahad]

For local development, consider looking into devd (https://github.com/cortesi/devd). It's a single binary that supports things like livereload, network throttling, routing, and reverse proxying.

[StavrosK]

Ooh, that looks pretty nice. I was using Caddy to serve the current directory, but this seems even nicer.

[sbarre]

I'd never heard of Caddy, and it looks great! Thanks for giving me something to tinker with this weekend! :-)

[zenlikethat]

Agreed, Caddy is great.

[aroch]

You do need to restart Caddy in order to renew your cert, FWIW

[mholt]

Not true - Caddy has always renewed certificates automatically, and the latest version (0.8.2) renews without restarting. Relevant change: https://github.com/mholt/caddy/commit/11103bd8d68ed9d8dcd2fc...