fix: run container as deployer's UID to fix volume permissions

Instead of chown (which requires sudo), set the container user to
match the deployer's UID/GID so it can write to the mounted data volume.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: hendisantika

.github/workflows/deploy-dev.yml

@@ -54,7 +54,7 @@ jobs:
 
       - name: Create app directory on server
         run: |
-          ssh deployer@103.31.204.189 'mkdir -p ~/jvmid-bot/data && sudo chown 1000:1000 ~/jvmid-bot/data'
+          ssh deployer@103.31.204.189 'mkdir -p ~/jvmid-bot/data'
 
       - name: Write .env file to server
         run: |
@@ -66,4 +66,4 @@ jobs:
 
       - name: Deploy on server
         run: |
-          ssh deployer@103.31.204.189 "cd ~/jvmid-bot && IMAGE_TAG=${{ github.run_number }} docker compose -f docker-compose.prod.yml pull && IMAGE_TAG=${{ github.run_number }} docker compose -f docker-compose.prod.yml up -d && docker image prune -f && echo 'Deployment complete (tag: ${{ github.run_number }}). Running containers:' && docker ps --filter 'name=jvmid-bot'"
+          ssh deployer@103.31.204.189 "cd ~/jvmid-bot && export UID=\$(id -u) GID=\$(id -g) && IMAGE_TAG=${{ github.run_number }} docker compose -f docker-compose.prod.yml pull && IMAGE_TAG=${{ github.run_number }} docker compose -f docker-compose.prod.yml up -d && docker image prune -f && echo 'Deployment complete (tag: ${{ github.run_number }}). Running containers:' && docker ps --filter 'name=jvmid-bot'"

docker-compose.prod.yml

@@ -2,6 +2,7 @@ services:
   bot:
     image: hendisantika/jvmid-bot:${IMAGE_TAG:-latest}
     container_name: jvmid-bot
+    user: "${UID:-1000}:${GID:-1000}"
     env_file: .env
     volumes:
       - ./data:/app/data