I added a new --compress option to enable compression.

Should it maybe be enabled by default? Maybe --compress-off instead 🤔

@francislavoie maybe should we choose if we want something "edge-ready" (and so, maybe should we also enable HTTPS by default, but then it will not be consistent with file-server) or something that will be put behind a proxy.

Currently, the commands mimic the behavior of file-server (no HTTPS by default), so I disabled compression by default. But I don't know the reasons why file-server doesn't use HTTPS by default.

"HTTPS by default" is only possible when a domain is specified anyway. That's how it works in the Caddyfile too. That's a key input that's required, since a name is needed for the SAN in the TLS cert (unless you use On-Demand TLS, but that's besides the point)

The caddy file-server command will use HTTPS if the --domain flag is specified with a domain name.

The caddy reverse-proxy command uses HTTPS if the --from value contains a domain name.

Maybe FrankenPHP could work similarly.

@mholt it currently does, but yes let's enable compression by default then!

(We should probably update caddy file-server to do the same; mostly an oversight I think that it didn't)

I'll open a PR on Caddy.