|
|
@@ -20,6 +20,7 @@ This project spans two machines. **Always check which machine you're operating o
|
|
|
- ssh into live: `ssh lucky@192.168.0.200`
|
|
|
- The live DB is at `/app/data/news.sqlite` in the container, which bind-mounts from `news_mcp/data/news.sqlite` on the host FS (relative to repo root).
|
|
|
- **Do NOT run maintenance/backfill scripts against the dev DB** — it's empty/stale. Either point explicitly to the live DB or tell the user to run it.
|
|
|
+- **Docker/DB path oddity:** docker-compose sets `NEWS_MCP_DB_PATH=./data/news.sqlite` (relative to `working_dir=/app`), so the container's DB is at `/app/data/news.sqlite`. But the host `.env` does NOT override this, so running the same script on the host resolves `DB_PATH` to the config default (`news_mcp/data/news.sqlite`) — a different, usually empty file. The docker-compose env vars only apply inside the container.
|
|
|
|
|
|
## Local Environment
|
|
|
- Source the repo-local `.venv` first when it exists.
|
