Hacker News Reader

Comment by cunthorpe | Hacker News Reader

To be fair, HTTPS by default makes perfect sense for a server. Of course the more complex the setup, the more you’re going against the defaults. It’s impossible to have defaults that work for everyone, so they chose the most common/desirable/sellable default.

View on HN

I'd argue that HTTPS by default makes perfect sense for a _public facing_ server. For something on an internal network it doesn't make as much sense, especially since that makes using the default path for getting certificates difficult (can't get certs if you don't have DNS).

I think what I'm trying to say is that Caddy was initially great for me (serving static files on the local network by IP address as an easy way to transfer files), but hasn't been that for ages.

FWIW, Caddy can act as its own CA, so it can issue certs for any private site, and you can add the root CA cert to any machines necessary.

> but hasn't been that for ages

Huh? It still is. This is all you need:

    :80 {
        root * /path/to/files
        file_server
    }

Or without a config file, simply:

    $ caddy file-server --root /path/to/files

Reply on news.ycombinator.com