Fix permission denied error on Unraid deployment

Resolved Docker container startup failures on Unraid /boot partition.

Changes:
- Remove development volume mount from docker-compose.yml
- Container now uses files baked into image during build
- Remove obsolete docker-compose version attribute
- Add permission fix in deploy.sh for /boot partition

The volume mount was causing permission issues by exposing /boot files
with restrictive permissions directly to the container.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

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

deploy.sh

@@ -37,6 +37,11 @@ else
     cd ${REMOTE_PATH}
 fi
 
+# Fix file permissions for Docker build (required for /boot partition)
+echo "Fixing file permissions..."
+chmod -R 755 ${REMOTE_PATH}
+chmod 644 ${REMOTE_PATH}/*.py ${REMOTE_PATH}/*.txt ${REMOTE_PATH}/*.md 2>/dev/null || true
+
 # Check if .env exists
 if [ ! -f .env ]; then
     echo "WARNING: .env file not found!"

docker-compose.yml

@@ -1,5 +1,3 @@
-version: '3.8'
-
 services:
   discord-stock-bot:
     build: .
@@ -9,9 +7,6 @@ services:
       - .env
     environment:
       - TZ=America/New_York
-    volumes:
-      # Mount source code for development (comment out for production)
-      - ./:/app
     logging:
       driver: "json-file"
       options: