Data & Assets
Dockerfiles, database seed files, generated Discord type data, and systemd unit examples used by AntiRaid.
The data/ directory holds static files, configs, and generated assets that services load at startup or that you use during deployment.
What's in here
| Path | Purpose |
|---|---|
docker/ | Dockerfiles and entrypoint scripts for each service (Postgres, SeaweedFS, Nginx, etc.) |
generated/ | Auto-generated JSON for Discord channel types, permission flags, and similar data. Services load this at runtime rather than hardcoding it. |
misc/ | Patches, test fixtures, and one-off data files |
seed.iblcli-seed | Database seed file — initializes Postgres with the tables and baseline data AntiRaid needs to run |
systemd-example/ | Example .service and .timer unit files for native (non-Docker) deployments |
Common tasks
Seeding the database — run the seed file using iblcli or your database setup script. This is a required step for any fresh deployment.
Docker deployments — the Dockerfiles in docker/ are what docker compose uses. You generally don't need to edit them unless you're customizing a service's build.
Native deployments — copy the unit files from systemd-example/ to /etc/systemd/system/, edit them to match your paths and environment, then run systemctl daemon-reload and systemctl enable --now <service>.
Generated assets — these are regenerated by running the relevant code-gen script in the project root. Don't edit them by hand; your changes will be overwritten the next time the script runs.
For more detail on deployment, see the Hosting guide.