Adding an optional anubis config by dessalines · Pull Request #285 · LemmyNet/lemmy-ansible
github.com
This adds an optional anubis, which stands in front of lemmy-ui only. It doesn't block or impede federation, or apps, only the lemmy-ui front end. I tested this via a fresh server, and it worked.

I’ve recently added anubis to lemmy.ml, and it seems to be working well.

I have a PR to add anubis to lemmy-ansible (our main installation method), and I could use some help tweaking / optimizing its botPolicy.yaml config, for federated services.

Anyone with experience running anubis, this would be much appreciated.

      • Otter@lemmy.caEnglish
        4·
        3 months ago

        We are not running Anubis, although we do block a large number of AI/LLM companies through IP addresses. Each time we block a new one, it makes a noticeable difference in the performance graphs.

  • olof@lemmy.mlEnglish
    2·
    3 months ago

    Not Lemmy specific, but I wanted to set up Anubis in a setup where I have one reverse proxy (nginx) handling many different domains. Last time I looked, it seemed to need one Anubis instance per domain. Is that still the case? Goal was to have a single Anubis instance and route all through it

    • Dessalines@lemmy.mlOPEnglish
      2·
      3 months ago

      I’m not an expert, but I think the fact that you need to set a TARGET in anubis, IE, where does anubis send you after passing it, means that you do need separate anubis’s for each site.