Add some additional help commands and a help script

no ref

- This should help users with the 'What next?' question at the end of their migration and gives them something to come back to once done

help

@@ -0,0 +1,48 @@
+#!/usr/bin/env bash
+
+cat << 'EOF'
+════════════════════════════════════════════════════════════════════
+                    GHOST DOCKER HELP & COMMANDS
+════════════════════════════════════════════════════════════════════
+
+COMMON COMMANDS:
+  docker compose logs -f ghost      # View real-time logs
+  docker compose logs -f caddy      # View Caddy webserver logs
+  docker compose ps                 # Check service status
+  docker compose down               # Stop all services
+  docker compose up -d              # Start all services
+  docker compose restart ghost      # Restart Ghost container
+
+TROUBLESHOOTING:
+  docker compose exec ghost sh      # Access Ghost container shell
+  docker compose logs --tail=100    # View last 100 log lines
+  docker stats                      # Monitor resource usage
+
+DATABASE ACCESS:
+  docker compose exec mysql mysql -u root -p
+  # Use the DATABASE_ROOT_PASSWORD from your .env file
+
+UPGRADES:
+  git pull                          # Pull latest updates
+  docker compose pull               # Get latest container images
+  docker compose up -d              # Upgrade to the latest version
+
+  For major upgrades, always:
+  1. Backup your data first
+  2. Read Ghost's release notes
+  3. Test in a staging environment
+
+CONFIGURATION:
+  - Edit .env file for environment variables
+  - Restart Ghost after changes: docker compose up -d
+
+USEFUL PATHS:
+  Content: ./data/ghost/
+  Database: ./data/mysql/
+  Logs: docker compose logs
+  Config: ./.env
+
+MORE HELP:
+  Ghost Docs: https://ghost.org/docs/
+  Ghost Community: https://forum.ghost.org/
+EOF