• Lemmy Automod Manager
  • Installation
  • Securing the API

This is a web GUI for Lemmy Automod.

You need to enable the management api for this UI to work. The management api should not be accessible over public networks. Additionally, if you use a custom build of this app (meaning you don't use the official docker image) and you enable server side rendering, you should make this UI inaccessible over a public network as well.

Don't forget to enable CORS for the management api.

Simply use the ghcr.io/rikudousage/lemmy-automod-manager docker image and configure the api URL using the environment variable API_URL.

For example, using docker compose:

replace http://127.0.0.1:4005 with any URL the management api is accessible on from your computer.

  automod:
    image: ghcr.io/rikudousage/lemmy-automod:dev
    environment:
      - MANAGEMENT_API_ENABLED=1
      - CORS_ALLOW_ORIGIN=^https?://(localhost|127\.0\.0\.1)(:[0-9]+)?$
      # configure the other environment variables according to your needs, see the automod readme for details
    ports:
      - 4005:80
  automod_manager:
    image: ghcr.io/rikudousage/lemmy-automod-manager:dev
    environment:
      - API_URL=http://127.0.0.1:4005
    ports:
      - 4006:80

The UI runs on port 80 in the container, in the example above it's bound to local port 4006.

Because all api requests are done client-side, you can install the UI anywhere (even locally) and simply expose the api to your computer - it doesn't have to run on the server at all.

The Automod README contains tips on securing the api: Securely accessing the api.