home-tracker A: point local app at Proxmox MySQL home_tracker (DB connectivity fix)

Attempted the .env wiring: set DB_CONNECTION=mysql, DB_HOST=192.168.1.213, DB_PORT=3306, DB_DATABASE=home_tracker, DB_USERNAME=home_tracker. BLOCKER: the operator-provided password `baseball` is the MySQL **root** password (matches homelab credentials.md), and the `home_tracker`@`%` app user REJECTS it — `SQLSTATE[HY000] [1045] Access denied for user 'home_tracker'@'192.168.1.165' (using password: YES)`. No `home_tracker` app-user password is stored anywhere in homelab (no secrets file under docker/home-tracker). .env is left pointed at the Proxmox MySQL but currently cannot authenticate. Need either the real `home_tracker` user password, or explicit OK to use root/baseball in .env (works now; poor practice). Until then home-tracker.test cannot connect.

# A — DB connectivity: point home-tracker.test at Proxmox MySQL `home_tracker` Child of epic #211. Decision (operator 2026-07-04): local app uses the Proxmox MySQL as single source of truth. ## Why home-tracker.test is on local SQLite, which lacks `monitored_services`/`probe_results` → "no such table" errors after login on `/gaming`. Real DB = Proxmox MySQL `home_tracker` @ 192.168.1.213:3306, verified (read-only) fully migrated (11 migrations) and populated: monitored_services=33, probe_results=477, task_completions=13, tasks=1, users=2, import_batches=1. ## Do - Update `.env`: `DB_CONNECTION=mysql`, `DB_HOST=192.168.1.213`, `DB_PORT=3306`, `DB_DATABASE=home_tracker`, `DB_USERNAME=home_tracker`, `DB_PASSWORD=<from homelab secrets>`. Use the dedicated `home_tracker`@`%` app user — NOT root. - Source the `home_tracker` user password: check homelab `docker/home-tracker` secret files / `credentials.md`, else ask operator. (First step; only real unblock needed.) - `php artisan config:clear`; verify `/gaming` (probes render), home/dashboard, and cat-feeding pages load against real data. `php artisan migrate:status` should show all applied / nothing pending. - Do NOT run migrations against Proxmox from dev. ## Caveat Local dev now reads/writes the live shared DB. For a 2-user home app likely fine; note for later — consider a separate dev DB / replica if risky. ## Done when home-tracker.test loads `/gaming` + cat-feeding with real data and no DB/table errors.

# A — DB connectivity: point home-tracker.test at Proxmox MySQL `home_tracker` Child of epic #211. Decision (operator 2026-07-04): local app should use the Proxmox MySQL as single source of truth. ## Why home-tracker.test is on local SQLite, which lacks `monitored_services`/`probe_results` → "no such table" errors after login on `/gaming`. The real DB is Proxmox MySQL `home_tracker` @ 192.168.1.213:3306, verified fully migrated (11 migrations) and populated: monitored_services=33, probe_results=477, task_completions=13, tasks=1, users=2, import_batches=1. ## Do - Update `.env`: `DB_CONNECTION=mysql`, `DB_HOST=192.168.1.213`, `DB_PORT=3306`, `DB_DATABASE=home_tracker`, `DB_USERNAME=home_tracker`, `DB_PASSWORD=<from homelab secrets>`. Use the dedicated `home_tracker`@`%` app user — NOT root. - Source the `home_tracker` user password: check homelab `docker/home-tracker` secret files / `credentials.md`, else ask operator. - `php artisan config:clear`; verify `/gaming` (probes render), home/dashboard, and cat-feeding pages load against real data. `php artisan migrate:status` should show all applied / nothing pending. - Do NOT run migrations against Proxmox from dev. ## Caveat Local dev now reads/writes the live shared DB. For a 2-user home app this is likely fine; note for later — consider a separate dev DB / replica if this becomes risky. ## Done when home-tracker.test loads `/gaming` + cat-feeding with real data and no DB/table errors.