fix: use shared core PostgreSQL for Coolify instead of separate instance

restic/compose.yaml

@@ -44,7 +44,6 @@ services:
       - backup_dev_gitea_config:/volumes/dev_gitea_config:ro
       - backup_dev_gitea_runner_data:/volumes/dev_gitea_runner_data:ro
       - backup_dev_coolify_data:/volumes/dev_coolify_data:ro
-      - backup_dev_coolify_postgres_data:/volumes/dev_coolify_postgres_data:ro
 
     environment:
       TZ: ${TIMEZONE:-Europe/Berlin}
@@ -171,9 +170,6 @@ volumes:
   backup_dev_coolify_data:
     name: dev_coolify_data
     external: true
-  backup_dev_coolify_postgres_data:
-    name: dev_coolify_postgres_data
-    external: true
 
 networks:
   compose_network:

restic/config.json

@@ -351,8 +351,7 @@
       "id": "coolify-backup",
       "repo": "hidrive-backup",
       "paths": [
-        "/volumes/dev_coolify_data",
-        "/volumes/dev_coolify_postgres_data"
+        "/volumes/dev_coolify_data"
       ],
       "schedule": {
         "cron": "0 0 * * *"