Comment on page
🐳
Running with Docker
Prerequisites
docker pull henrykoleoso/in-house-queue:v[latest-version]
You can also pull the latest image with the following:
docker pull henrykoleoso/in-house-queue
- 2.
- 3.Start the bot
docker run -d \
--name in-house-queue \
--restart on-failure \
--env-file .env \
-v inhouse-db:/app/db \
henrykoleoso/in-house-queue
- 3.It would be best to restart the bot again for all database tables to generate.
docker stop in-house-queue
docker start in-house-queue
Any errors relating to "persistent_lb" can be ignored. You probably have not created that leaderboard yet!
version: '3.8'
services:
bot:
image: henrykoleoso/in-house-queue
# create a .env file in the root directory
environment:
TOKEN: ${TOKEN}
TOP: ${TOP}
JUNGLE: ${JUNGLE}
MID: ${MID}
SUPPORT: ${SUPPORT}
ADC: ${ADC}
# Roles for Valorant
CONTROLLER: ${CONTROLLER}
DUELIST: ${DUELIST}
INITIATOR: ${INITIATOR}
SENTINEL: ${SENTINEL}
# Roles for Overwatch
TANK: ${TANK}
DPS: ${DPS}
SUPPORT_OW: ${SUPPORT_OW}
# Discord ID of Owners. Use the SAME ID for BOTH values if there is only 1 owner.
DEV_1: ${DEV_1}
DEV_2: ${DEV_2}
# Guild/Server ID of where the bot is running. Use the SAME ID for BOTH values if there is only 1 server.
GUILD_1: ${GUILD_1}
GUILD_2: ${GUILD_2}
# Discord ID of the Bot
BOT_ID: ${BOT_ID}
# Discord ID of the Error Log channel. Use the SAME ID for BOTH values if there is only 1 error log channel.
ERROR_LOG_CHANNEL_ID_1: ${ERROR_LOG_CHANNEL_ID_1}
ERROR_LOG_CHANNEL_ID_2: ${ERROR_LOG_CHANNEL_ID_2}
volumes:
- inhouse-db:/app/db
restart: on-failure
volumes:
inhouse-db:
-v db:/app/db
Creates a named volume called inhouse-db.
This volume is attached to the docker container and contains your DATABASE file. It has all the crucial data about your server, leaderboard, set channels, wins, etc. You can pull a new version anytime; the data will persist if you rerun the docker run
command. You can start here to learn more about how docker volumes work.Please make sure the bot has enough permissions. For this particular use case, we suggest providing the bot admin rights.
Last modified 1mo ago