Fernlight serves a folder over HTTPS with sensible defaults: automatic certificates, compression, caching headers and range requests. One binary, one config file, zero dependencies.
# start serving the current folder $ fernlight serve ./public --domain example.org fernlight v0.9.4 root ./public listen :443 (h2, h3) :80 → https tls certificate ready (ACME) cache etag + immutable for /assets/* compress br, gzip ready in 38 ms GET / 200 3.1 kB 0.4 ms GET /assets/app.js 200 41.2 kB 0.6 ms GET /video.mp4 206 1.0 MB range
Fernlight is intentionally small. It does one job and tries to do it well.
Certificates are requested and renewed on their own. HTTP redirects to HTTPS.
HTTP/2 and HTTP/3 out of the box, with graceful fallback to HTTP/1.1.
Precompressed files are picked up automatically, others compressed on the fly.
ETags, Last-Modified and immutable headers for fingerprinted assets.
Resumable downloads and seekable video and audio without extra setup.
Change the config and send SIGHUP. Open connections are not dropped.
Most sites never need more than a few lines.
Any directory with an index.html works.
Fernlight handles the certificate.
A systemd unit is included in every release.
[site] domain = "example.org" root = "/var/www/public" [cache] immutable = ["/assets/*"] max_age = "1h" [compress] formats = ["br", "gzip"] [log] level = "warn" # no access logs by default
Small static files, keep-alive connections, single instance. Results vary with hardware and network.
| Scenario | Requests / s | p99 latency |
|---|---|---|
| index.html, 3 kB | 48,200 | 1.9 ms |
| JS bundle, 40 kB (br) | 21,700 | 3.4 ms |
| Image, 400 kB | 3,100 | 11 ms |
| Video range, 1 MB | 940 | 28 ms |