Created November 27, 2021 by Dr. Romulus
Bot for Manechat Management
Get started by posting .help
and/or .config
in one of the private bots-* channels. From there you can explore Izzy's self-documentation for all commands and configuration items. You don't need to read all of them, but browsing them should give you a pretty good idea what she can do.
Izzy-Moonbot/Docker Compose/Dev/appsettings.json
. This contains secrets such as Discord tokens and database credentials that we don't want to store in GitHub.appsettings.json
, so your instance of Izzy will give you developer permissions.appsettings.json
file on Izzy's production environment.cd
over to <your local repo clone>/Izzy-Moonbot/Docker Compose/Dev
, then running docker compose up
should launch Izzy and connect her to our Bot Testing server, after which she should start responding to Discord messages there.
docker compose up -d
if you don't want Docker taking over control of your terminal.~/.ssh/authorized_keys
file on Izzy's production host machine. If you don't have SSH keys already, there are many ways to generate a keypair. Feel free to ask for help generating a keypair if you need it. Using ed25519
keys instead of rsa
keys is highly recommended.
git
commits, also on every git operation)Once all the changes you want to release have been merged onto the mane
branch, wait for CI to complete building the Docker images. Image builds are handled by GitHub Actions and are automatically uploaded to GitHub Container Registry. If you have multiple PRs to release/merge into mane
, give each CI a few minutes to run before releasing the next one to avoid CI run and package upload conflicts.
Once CI is complete and images are built, the below is the release process for now, until further changes are implemented.
cd izzy-compose
docker compose up -d --force-recreate --no-deps izzy
docker logs izzymoonbot-izzy-1 -f
to monitor Izzy's logs, or access them via the Portainer UI. Logs do not persist between container recreations.