6 ms·

Just using caddy server seems a lot simpler...

• qrv3w 11y ago
  +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!
• sbarre 11y ago
  I'd never heard of Caddy, and it looks great! Thanks for giving me something to tinker with this weekend! :-)
• tlrobinson 11y ago
  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 11y ago
    For local development, consider looking into devd (https://github.com/cortesi/devd https://github.com/cortesi/devd). It's a single binary that supports things like livereload, network throttling, routing, and reverse proxying.
    • StavrosK 11y ago
      Ooh, that looks pretty nice. I was using Caddy to serve the current directory, but this seems even nicer.
• aroch 11y ago
  You do need to restart Caddy in order to renew your cert, FWIW
  • mholt 11y ago
    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/11103bd8d68ed9d8dcd2fc0960c5d206175e1b1f#diff-e4b0eb464d8c2d83155310aff515dd9a https://github.com/mholt/caddy/commit/11103bd8d68ed9d8dcd2fc...
• zenlikethat 11y ago
  Agreed, Caddy is great.