fixing permission issues
CI/CD / build (push) Successful in 44s
CI/CD / deploy (push) Successful in 9s

This commit is contained in:
2026-07-10 01:13:26 +02:00
parent be360843eb
commit 25cbe3bd56
2 changed files with 10 additions and 1 deletions
+2
View File
@@ -51,6 +51,8 @@ jobs:
# Ship the compose file and Lavalink config to the server. .env and
# catchphrases.txt live on the server and are intentionally not copied.
# Plugins live in a named Docker volume (see docker-compose.yaml), so
# only the lavalink/ dir for application.yml is needed here.
ssh -i ~/.ssh/key $HOST "mkdir -p $DIR/lavalink"
scp -i ~/.ssh/key docker-compose.yaml $HOST:"$DIR/docker-compose.yaml"
scp -i ~/.ssh/key lavalink/application.yml $HOST:"$DIR/lavalink/application.yml"
+8 -1
View File
@@ -34,6 +34,13 @@ services:
- LAVALINK_SERVER_PASSWORD=${LAVALINK_PASSWORD}
volumes:
- ./lavalink/application.yml:/opt/Lavalink/application.yml:ro
- ./lavalink/plugins/:/opt/Lavalink/plugins/
# Named volume (managed by Docker) rather than a host bind mount. Docker
# initializes it from the image, so it's owned by Lavalink's container user
# and the plugin jars download without permission errors. No root-owned (or
# UID-mismatched) plugins/ dir in the deploy directory.
- lavalink-plugins:/opt/Lavalink/plugins
ports:
- "2333:2333"
volumes:
lavalink-plugins: