62cdb8a9b8
This may be relevant for #206, although unsure if this is actually a fix. |
||
---|---|---|
.github | ||
docs | ||
PluralKit.API | ||
PluralKit.Bot | ||
PluralKit.Core | ||
PluralKit.Tests | ||
scripts | ||
.dockerignore | ||
.editorconfig | ||
.gitignore | ||
.gitmodules | ||
BRANCHRENAME.md | ||
docker-compose.yml | ||
Dockerfile | ||
netlify.toml | ||
nuget.config | ||
pluralkit.conf.example | ||
PluralKit.sln | ||
README.md |
PluralKit
PluralKit is a Discord bot meant for plural communities. It has features like message proxying through webhooks, switch tracking, system and member profiles, and more.
Do you just want to add PluralKit to your server? If so, you don't need any of this. Use the bot's invite link: https://discord.com/oauth2/authorize?client_id=466378653216014359&scope=bot&permissions=536995904
PluralKit has a Discord server for support, feedback, and discussion: https://discord.gg/PczBt78
Requirements
Running the bot requires .NET Core (v3.1) and a PostgreSQL database. It should function on any system where the prerequisites are set up (including Windows).
Optionally, it can integrate with Sentry for error reporting and InfluxDB for aggregate statistics.
Configuration
Configuring the bot is done through a JSON configuration file. An example of the configuration format can be seen in pluralkit.conf.example
.
The configuration file needs to be placed in the bot's working directory (usually the repository root) and must be called pluralkit.conf
.
The configuration file is in JSON format (albeit with a .conf
extension). The following keys are available (using .
to indicate a nested object level), bolded key names are required:
PluralKit.Bot.Token
: the Discord bot token to connect withPluralKit.Database
: the URI of the database to connect to (in ADO.NET Npgsql format)PluralKit.Bot.ClientId
(optional): the ID of the bot's user account, used when generating invite links throughpk;invite
. It's automatically determined if not present, but overriding it may be useful for private instances that still want a public invite link.PluralKit.SentryUrl
(optional): the Sentry client key/DSN to report runtime errors to. If absent, disables Sentry integration.PluralKit.InfluxUrl
(optional): the URL to an InfluxDB server to report aggregate statistics to. An example of these stats can be seen on the public stats page.PluralKit.InfluxDb
(optional): the name of an InfluxDB database to report statistics to. If either this field orPluralKit.InfluxUrl
are absent, InfluxDB reporting will be disabled.PluralKit.LogDir
(optional): the directory to save information and error logs to. If left blank, will default tologs/
in the current working directory.
The bot can also take configuration from environment variables, which will override the values read from the file. Here, use :
(colon) or __
(double underscore) as a level separator (eg. export PluralKit__Bot__Token=foobar123
) as per ASP.NET config.
Running
Docker
The easiest way to get the bot running is with Docker. The repository contains a docker-compose.yml
file ready to use.
- Clone this repository:
git clone https://github.com/xSke/PluralKit
- Create a
pluralkit.conf
file in the same directory asdocker-compose.yml
containing at least aPluralKit.Bot.Token
field- (
PluralKit.Database
is overridden indocker-compose.yml
to point to the Postgres container)
- (
- Build the bot:
docker-compose build
- Run the bot:
docker-compose up
In other words:
$ git clone https://github.com/xSke/PluralKit
$ cd PluralKit
$ cp pluralkit.conf.example pluralkit.conf
$ nano pluralkit.conf # (or vim, or whatever)
$ docker-compose up -d
Manually
- Install the .NET Core 3.1 SDK (see https://dotnet.microsoft.com/download)
- Clone this repository:
git clone https://github.com/xSke/PluralKit
- Create and fill in a
pluralkit.conf
file in the same directory asdocker-compose.yml
- Run the bot:
dotnet run --project PluralKit.Bot
- Alternatively,
dotnet build -c Release -o build/
, thendotnet build/PluralKit.Bot.dll
- Alternatively,
(tip: use scripts/run-test-db.sh
to run a temporary PostgreSQL database on your local system. Requires Docker.)
Upgrading database from legacy version
There are a few adjustments to do for the new versions of PluralKit to work with a legacy PluralKit database :
- Dump the database (you never know what may happen !)
- Upgrade the database by firing those lines in psql (or by putting them in an sql file and giving it to postgres) :
do $$ begin
create type proxy_tag as (
prefix text,
suffix text
);
exception when duplicate_object then null;
end $$;
alter table members add column IF NOT EXISTS display_name text;
alter table members add column IF NOT EXISTS proxy_tags proxy_tag[] not null default array[]::proxy_tag[];
alter table members add column IF NOT EXISTS keep_proxy bool not null default false;
update members set proxy_tags = array[(members.prefix, members.suffix)]::proxy_tag[] where members.prefix is not null or members.suffix is not null;
alter table members drop column IF EXISTS prefix cascade;
alter table members drop column IF EXISTS suffix cascade;
alter table messages add column IF NOT EXISTS original_mid bigint;
alter table servers add column IF NOT EXISTS log_blacklist bigint[] not null default array[]::bigint[];
alter table servers add column IF NOT EXISTS blacklist bigint[] not null default array[]::bigint[];
- Start PluralKit and let it finish the automatic database upgrades
Documentation
License
This project is under the Apache License, Version 2.0. It is available at the following link: https://www.apache.org/licenses/LICENSE-2.0