How to use Anubis with Caddy on 443 with file_server?

[herzenschein]

https://anubis.techaro.lol/docs/admin/environments/caddy mentions how to use it for services running on a given port, but I can't find a way to use it for a main website on port 443 using file_server.

Like:

example.com {
    root * /srv/mywebpage
    file_server
}

[OptionalM]

Here's one way to do it, but it's running an additional caddy. The first one for TLS termination, then Anubis, and then another caddy for the file_server.

Personally, I'm not really happy with that and hope that someone can come up with a way that doesn't require more caddies 🥴

[OptionalM]

Issue #16 regards a module/middleware for caddy, which would allow you to just plop a line into your Caddyfile to have anubis sit there. They mention daebalus/caddy-anubis, which is still in an early state, but is usable if you want to try it.

[herzenschein]

I tested it, it works very well. I don't see the slowness issues mentioned in the issue and repo.

I had to build my own Caddy container with the plugin as documented in https://hub.docker.com/_/caddy#adding-custom-caddy-modules. The only confusion I had was that I needed to build on arm64 for it to work on my Raspberry Pi (I couldn't just specify --arch=arm64 when building it).

And then just do something like this:

mywebsite.com {
    root * /srv/mywebsite
    file_server
    anubis
    request_header +X-Real-IP {remote_host}
    request_header +X-Forwarded-For {remote_host}
}

Works with everything I use (file_server, file_server browse, reverse_proxy), which is nice because now I don't need to get an Anubis instance up for every single service.