docker build -f Dockerfile . --tag core:twilight --no-cache
docker run --rm -d -p 6972:80 --env-file .env --name twilight core:twilight
docker build -f Dockerfile . --tag core:jobs --no-cache
docker run --rm -d -p 6974:6974 --env-file .env --name jobs --link redis:redis --link postgres:postgres --net database_default --env docker=true --env version=v2 core:jobs
docker build -f Dockerfile . --tag core:bot --no-cache
- no1:
docker run --rm -d -p 7777:7777 --env-file .env --name bot1 --link redis:redis --link postgres:postgres --net database_default --env docker=true --env uuid=no1 --env version=v2 core:bot
- no2:
docker run --rm -d -p 7777:7777 --env-file .env --name bot2 --link redis:redis --link postgres:postgres --net database_default --env docker=true --env uuid=no2 --env version==v2 core:bot
docker compose up --build --no-cache
docker compose up -d
docker pull fredboat/lavalink
docker run --rm -d -p 3333:3333 -v application.yml:/opt/Lavalink/application.yml --name lavalink fredboat/lavalink:latest
docker image ls
docker system df
docker system prune (-a)
- remove errored image
docker rmi $(docker images -f "dangling=true" -q)
- Add additional database settings in here
- Check docker-compose.yml setting
- Run
docker run blablabla
-
Set
USE_TWILIGHT
totrue
in bot's env file -
SET
USE_TWILIGHT
totrue
in job's env file -
If you set
USE_TWILIGHT
totrue
, also setTWILIGHT_HOST
andTWILIGHT_PORT
-
If not, just ignore this whole path
-
Check Dockerfile setting
-
Run
docker run blabla
- Check Dockerfile for jobs
- Run
docker run blabla
- Check Dockerfile for app
- Run
docker run blabla
-
For non-metrics twilight-http-proxy, execute
-
cargo build --release
and -
BOT_TOKEN="your bot token" PORT="port to expose, see Dockerfile" ./target/release/twilight-http-proxy
-
For metrics twilight-http-proxy, execute
-
cargo build --release --features expose-metrics
and -
BOT_TOKEN="your bot token" PORT="port to expose, see Dockerfile" ./target/release/twilight-http-proxy