fix: use relative paths for postgres data and backups to avoid root permission issues

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

.gitea/workflows/deploy.yml

@@ -39,14 +39,14 @@ jobs:
 
       - name: Backup database before deploy
         run: |
-          mkdir -p /opt/galaxis-po/backups
+          mkdir -p ./data/backups
           docker exec galaxis-po-db pg_dump -U ${{ secrets.DB_USER }} ${{ secrets.DB_NAME }} \
-            > /opt/galaxis-po/backups/$(date +%Y%m%d_%H%M%S).sql 2>/dev/null || true
+            > ./data/backups/$(date +%Y%m%d_%H%M%S).sql 2>/dev/null || true
 
       - name: Ensure data directories exist
         run: |
-          mkdir -p /opt/galaxis-po/postgres-data
-          mkdir -p /opt/galaxis-po/backups
+          mkdir -p ./data/postgres
+          mkdir -p ./data/backups
 
       - name: Deploy with Docker Compose
         run: |

.gitignore

@@ -54,6 +54,7 @@ Thumbs.db
 # Database
 *.db
 *.sqlite3
+data/
 
 # Test
 .coverage

docker-compose.prod.yml

@@ -10,7 +10,7 @@ services:
       POSTGRES_PASSWORD: ${DB_PASSWORD}
       POSTGRES_DB: ${DB_NAME}
     volumes:
-      - /opt/galaxis-po/postgres-data:/var/lib/postgresql/data
+      - ./data/postgres:/var/lib/postgresql/data
     healthcheck:
       test: ["CMD-SHELL", "pg_isready -U ${DB_USER} -d ${DB_NAME}"]
       interval: 5s