This project revolves around a heavily configurable and
data-based Discord Bot. Don't try understanding it, k?
All I did was abuse the heck out of the 'raw' Discord.JS
Event, effectively handling all packets without a real
event handler. The only thing I really use Discord.JS for
is to send packets. I really didn't want to program
those as well. Why do I do this? Well, first of all,
cuz I can. Second: it fixes a few issues and lifts some
limitations, such as the fact that I couldn't process
messages, which were sent before the bot was started up!
So that took me here. You can try understanding the
project, but if you wanna contribute, I'd highly suggest
hitting me up, so I can walk you through the mess I
produced!
You can self-host this project. For that you need to setup a few things. Pre-Requisites are:
- Git
- Docker
- Docker-Compose
- Running Docker Daemon / Service
- Node.JS
- PNPM
- FFMPEG
- Discord Bot Token[s]
- Spotify API Credentials
- Google API Key
Then you need to setup:
- Git Clone this Repository
- Run
pnpm install
in the local repo - Setup Docker Secrets at
./secrets/{db_pass,db_user}
- Setup
.env
-file, with:- build_token: production discord token
- dev_token: dev discord token
- db_port: Port for the DB (same as configured in
docker-compose.yml
) - db_name: Name for the DB (...)
- db_user: User for the DB (...)
- db_pass: Password for the DB (...)
- spotify_client: Spotify Client ID
- spotify_secret: Spotify Secret Key
- youtube_key: Google (YouTube) API Key
Note: You can message Doomer#3316 or Go#3741 via Discord for suggestions! [or submit an issue with the suggestion tag]
Yes, I need to include this, for this is music, I code with, which keeps me sane. Thanks to those artists my bug fixing journey becomes a bit more pleasant!