Refactor bambuddy service volumes in compose.yaml for clarity and consistency

komodo/automate/bambuddy/.env.sample

@@ -1,3 +1,4 @@
 PG_USER=bambuddy
 PG_PASS=changeme
 DATA_PATH=/mnt/data
+LOGS_PATH=/mnt/logs

komodo/automate/bambuddy/compose.yaml

@@ -4,15 +4,13 @@ services:
     container_name: bambuddy
     network_mode: host  # Recommended for automatic printer discovery
     volumes:
-      - bambuddy_data:/app/data
-      - bambuddy_logs:/app/logs
-      - ${DATA_PATH}/media/projects:/external/nas
+      - ${DATA_PATH}:/app/data
+      - ${LOGS_PATH}:/app/logs
     environment:
       - PUID=${PUID:-1000}
       - PGID=${PGID:-1000}
       - TZ=America/Toronto  # Your timezone
       - TRUSTED_FRAME_ORIGINS=http://homeassistant.local:8123
-      - BAMBUDDY_EXTERNAL_ROOTS=/external/nas
       - PORT=8870
     restart: unless-stopped
     # Docker SIGKILLs after 10s by default. Bambuddy stops well inside that,
@@ -20,5 +18,4 @@ services:
     # can still checkpoint the database instead of being killed mid-write.
     stop_grace_period: 30s
 volumes:
-  bambuddy_data:
   bambuddy_logs: