update

Author: Admin9705

.cursor/rules/huntarr-dev.mdc

@@ -18,11 +18,11 @@ alwaysApply: true
 - Test both Docker and local environments (port 9705)
 
 ### UNRAID DEPLOYMENT (huntarr-moviehunt) — ALWAYS AFTER CODE CHANGES
+- **Always deploy our LOCAL build, never pull from Docker Hub.** Use `./unraid/deploy-with-build.exp`, which copies this repo’s source to Unraid, builds the image there, and runs it. Do **not** use `deploy-moviehunt-with-mounts.exp` or `deploy-moviehunt.exp` for normal deploys—those scripts run `huntarr/huntarr:latest` from Docker Hub, which is a published release and is not this repo’s current code.
 - **Deploy target: always Unraid unless the user explicitly says to do it locally.** When they ask to deploy, redeploy, or run the container, use Unraid. Only use local Docker when they say "local" or "run it locally". If Unraid deploy fails, then run local Docker.
 - **ALWAYS redeploy to Unraid after making code changes** (run `./unraid/deploy-with-build.exp`). Do not wait for the user to ask.
 - When the user asks to **deploy**, **redeploy**, or **deploy the Huntarr container to Unraid**, they mean the **huntarr-moviehunt** test container on Unraid (10.0.0.10).
-- Use the project’s Unraid scripts: `./unraid/deploy-with-build.exp` (default), `./unraid/deploy-moviehunt-with-mounts.exp` for full deploy with volume mounts, or `./unraid/deploy-moviehunt.exp` for appdata-only.
-- Default full deploy: `cd /Users/home/Huntarr/Huntarr.io && ./unraid/deploy-with-build.exp`
+- Unraid deploy command: `cd /Users/home/Huntarr/Huntarr.io && ./unraid/deploy-with-build.exp` (builds from source on Unraid; same volume mounts as the other scripts).
 - Connection/details live in `./unraid/` (README, DEPLOYMENT.md, STATUS.md, TESTING-GUIDE.md). The `./unraid/` directory is git-ignored.
 
 ### VERSION MANAGEMENT

.cursor/rules/unraid-always-redeploy.mdc

@@ -5,9 +5,11 @@ alwaysApply: true
 ---
 # Unraid: Always Redeploy After Code Changes
 
+- **Always deploy our LOCAL build, never the image from Docker Hub.** Pulling `huntarr/huntarr:latest` from Docker Hub would deploy a published release (often older than this repo). We deploy what we have here: build from this repo’s source and deploy that.
 - **Deploy target: always Unraid unless the user explicitly says to do it locally.** When they ask to deploy, redeploy, or run the container, use Unraid. Only use local Docker when they say "local" or "run it locally".
 - **After making any code changes to Huntarr, ALWAYS run the Unraid deploy.** Do not wait for the user to ask. Do it automatically so they can test immediately.
 - Command: `cd /Users/home/Huntarr/Huntarr.io && ./unraid/deploy-with-build.exp`
-- This builds from source and deploys to the huntarr-moviehunt container on Unraid (10.0.0.10). URL: http://10.0.0.10:9720
+- This copies local source to Unraid, builds the image there (`huntarr-moviehunt-local:latest`), and deploys to the huntarr-moviehunt container on Unraid (10.0.0.10). URL: http://10.0.0.10:9720
+- **Do not use** `./unraid/deploy-moviehunt-with-mounts.exp` for normal deploys—that script uses `huntarr/huntarr:latest` from Docker Hub, not our local code.
 - Run this at the end of the conversation turn whenever you have modified project source files (Python, JS, HTML, CSS, templates, etc.).
 - If Unraid deploy fails (e.g. unreachable), then run local: `docker-compose down && COMPOSE_BAKE=true docker-compose up -d --build`.