shaderBOT

The following information is for developers and contributors. If you're a user, please go to the wiki instead.

Install Dependencies

bun install

Use the --production flag to only install runtime dependencies. The --frozen-lockfile flag can be used to enforce the usage of the exact versions specified in the lock file and prevent it from being modified.

Configuration (required)

Discord Application

You must enable the "Server Members Intent" and "Message Content Intent" switches in the "Bot" tab of your Discord application in order for some features to work.

Settings

The file customContent/settings.jsonc contains information specific to the bot (e.g. the ID of the guild) and should match the setup on your server. Its content should not include any sensitive information, since it may be publicly displayed while configuring the bot.

There is a template configuration in settings.template.jsonc, which contains the necessary structure and documents what each option does. Using this template, you must manually create and adjust customContent/settings.jsonc before starting shaderBOT. Once it is running, you can use commands to modify the configuration.

WARNING: Most invalid options will crash shaderBOT or silently skip the desired action as soon as they are accessed! shaderBOT will check the types of all configuration values at startup, but it can not check their validity.

Environment Variables

Environment variables are read from .env and specifiy sensitive information like private keys that shouldn't ever be publicly visible.

Name	Default	Description
TOKEN	NONE	The token which you can find under the "Bot" tab of your Discord application.
APPLICATION_CLIENT_ID	NONE	The client ID which you can find under the "General Information" tab of your Discord application.
APPLICATION_CLIENT_SECRET	NONE	The client secret which you can find under the "General Information" tab of your Discord application.
BACKUP_ENCRYPTION_KEY	NONE	The key used for encrypting and decrypting channel backups. It must be 256 bits (32 characters) long.
SESSION_SECRET	NONE	The secret key used for signing session cookies. It is required if BOT_ONLY is not set to true.
NODE_ENV	production	The environment this is being run in. Can be either development or production and should always be set accordingly.
PORT	3001	The port that the HTTP API will run on.
UDS_PATH	NONE	The UNIX domain socket that the HTTP API will run on. Takes precedence over PORT if specified.
UDS_UID	NONE	The UID of the user that will own the UNIX domain socket file.
UDS_GID	NONE	The GID of the group that will own the UNIX domain socket file.
DOMAIN	localhost	The domain that the HTTP API will run on.
BOT_ONLY	false	Run the application in bot-only mode, which disables the HTTP server.
PG_USER	postgres	The name used for accessing the PostgreSQL database.
PG_PASSWORD	postgres	The password used for accessing the PostgreSQL database.
PG_HOST	localhost	The hostname used for connecting to the PostgreSQL server.
PG_PORT	5432	The port which the PostgreSQL server is running on.
PG_DATABASE	shaderBOT	The name of the PostgreSQL database.

UNIX Domain Sockets

For using UNIX domain sockets, set the UDS_PATH environment variable to e.g. /run/shaderbot/web-api.sock. The socket file has read and write permissions for the user and group that owns it, i.e. only processes by the same user or in the same group can bind to it.

By default, the UID and GID of the file are left untouched. You can override them using the UDS_UID and UDS_GID environment variables.

If the API runs through a reverse proxy like NGINX, which is usually in the www-data group, grab the GID (getent group www-data) and set it accordingly.

Running the Application

bun (development)

bun run dev

This will run the application and watch for changes. You can also manually run the application without watching for changes using bun run start.

PM2 (production)

pm2 start ecosystem.config.cjs

This will daemonize and run the application with PM2 using the ecosystem.config.cjs configuration file.

Docker (production)

Move the files in /scripts/prod/docker/ to the root folder of this project. After configuring the Dockerfile, you can create and start the container using docker-compose:

docker-compose up

IMPORTANT: The Docker configuration is mostly untested, so you should expect issues when using it.

Uploading Command Structure

You must upload the command structure to Discord in order to be able to view and use commands. You can do that by running the following command after building the application:

bun run update

Updating the Application

In order to update the application to the newest version, pull the latest changes from GitHub. After rebuilding the source code, you must restart the application for the changes to take effect.

Be aware that new settings could have been added to the configuration file. The console output will inform you about any missing keys and the application will only start after they have been added.

Additionally, re-uploading the command structure may be neccessary if it has changed.

Recommended Visual Studio Code Settings and Extensions

Settings

Adding the following options to your VS Code configuration file is highly recommended:

"files.exclude": {
    "**/.git": true,
    "**/.svn": true,
    "**/.hg": true,
    "**/CVS": true,
    "**/.DS_Store": true,

    "**/*.js": { "when": "$(basename).ts" },
    "**/*.js.map": true
},
"[typescript]": {
    "editor.defaultFormatter": "esbenp.prettier-vscode",
    "editor.formatOnSave": true,
    "editor.codeActionsOnSave": {
        "source.organizeImports": true
    }
},

This will hide the transpiled JavaScript files if there are corresponding TypeScript files and automatically format when saving.

Extensions

• Prettier - Code formatter - Used for auto-formatting to improve consistency. It will use the existing configuration file (.prettierrc).
• SQL tagged template literals (syntax only) - SQL syntax highlighting.

Made by Kneemund