A module for Caddy

[miku-orb]

It would be nice if this could be possible to be built directly as a Caddy module (since both are Go programs), this way it could be easily used within it (as request middleware), without complex/error-prone/inefficient request routing to an external process. (and thus more adoption, since it'd be very straightforward)

Ideally it'd allow reconfiguring options, both defaults on global level and per-path, this way people would have full freedom of choice on which paths to enable Anubis if not on all, and fine-tune some settings on some specific ones if needed.

As an inspiration for similar approach taken by another project, look at: https://github.com/darkweak/souin/tree/master/plugins/caddy

Souin cache is structured as a library, but offers plugins, including Caddy, to directly use it within the web servers (though in its case, the docs are a bit lacking), with the file structure that it has, it can easily be added to Caddy with

xcaddy build --with github.com/darkweak/souin/plugins/caddy

Other examples include: github.com/dunglas/mercure/caddy, github.com/dunglas/vulcain/caddy

[Xe]

Depends on #9, but this is very doable!

[miku-orb]

Nice! Been keeping an eye on Anubis ever since the first blog post, glad it made its way onto a separate repo now. I imagine with a module build like this it could take off similarly to Caddy-Defender (similar project in purpose, but taking a different approach)

[asyncmeow]

Depends on #9, but this is very doable!

Now that #9 is completed, is there a Caddy module in the works? That would be the ideal way to deploy Anubis in my setup, so that's the only thing keeping me from using it

[Xe]

It's in the works! More refactoring is required but it will make the code more maintainable.

[JasonLovesDoggo]

Nice! Been keeping an eye on Anubis ever since the first blog post, glad it made its way onto a separate repo now. I imagine with a module build like this it could take off similarly to Caddy-Defender (similar project in purpose, but taking a different approach)

Haha, it's nice to see my project here! It definitely would be nice to have a modular architecture (swappable responders/matchers) in anubis like in defender. I already have the the ranges module, which I would like to integrate into anubis (see https://github.com/JasonLovesDoggo/caddy-defender#embedded-ip-ranges)

@/Xe, if there is any help needed for the caddy module, I'm more than happy to write that part

[daegalus]

Just a heads up, I have started prototyping a caddy module here: https://github.com/daegalus/caddy-anubis it "works", but has some warts. You are welcome to contribute or point out issues/test it. It works with the current Anubis ServeHTTP style of doing things.

[JasonLovesDoggo]

Just a heads up, I have started prototyping a caddy module here: https://github.com/daegalus/caddy-anubis it "works", but has some warts. You are welcome to contribute or point out issues/test it. It works with the current Anubis ServeHTTP style of doing things.

Ooo looks nice! My only issue with it is that it relies on the Anubis config vs a caddyfile adapter. Though I only took a 12-second look so it might not be possible with Anubis ATM.

[PhotonQuantum]

Just a heads up, I have started prototyping a caddy module here: https://github.com/daegalus/caddy-anubis it "works", but has some warts. You are welcome to contribute or point out issues/test it. It works with the current Anubis ServeHTTP style of doing things.

Awesome! I also tried to port anubis to caddy but now my project is evolving into an individual one. However, I guess what I'm doing for anubis specific routes would be helpful to your implementation.

https://github.com/sjtug/cerberus/tree/master/directives

So I split it into three directives: App (global config and state init), Endpoint (challenge and static assets), and Middleware (validating cookie), and they share the same internal state. I think you can do something similar to anubis, like sharing the same libanubis instance among all three directives.

[daegalus]

Just a heads up, I have started prototyping a caddy module here: https://github.com/daegalus/caddy-anubis it "works", but has some warts. You are welcome to contribute or point out issues/test it. It works with the current Anubis ServeHTTP style of doing things.

Awesome! I also tried to port anubis to caddy but now my project is evolving into an individual one. However, I guess what I'm doing for anubis specific routes would be helpful to your implementation.

https://github.com/sjtug/cerberus/tree/master/directives

So I split it into three directives: App (global config and state init), Endpoint (challenge and static assets), and Middleware (validating cookie), and they share the same internal state. I think you can do something similar to anubis, like sharing the same libanubis instance among all three directives.

This is superb, thank you for the example, this gives me ideas on how to improve the Caddy plugin to work properly. Thanks!

[z0xca]

bump

[daegalus]

Sorry guys, i am still planning to make the Caddy middleware production ready. I just have been quite busy with RL stuff and family summer vacations. I plan to get back to it soon.