food/deploy/food.service, branch auth

Phase 2: session auth for the web UI

2026-06-23T19:37:48+00:00

Require login for /app/, with a long sliding session so you log in once per device and effectively stay in. - AppLoginRequiredMiddleware gates only /app/; /api/ keeps DRF token auth and /admin/ keeps its own login (a blanket LoginRequired would break token requests, whose user isn't resolved until the view runs). - Login page (styled to the dark palette) via django.contrib.auth.urls; logout control in the nav. - Session: ~1 year cookie, sliding (saved every request), survives browser close. - Dropped every @csrf_exempt now that a real session + CSRF token are in place (HTMX already sends X-CSRFToken). - SECRET_KEY and DEBUG now read from the environment (prod-safe defaults); systemd loads an optional /var/lib/food/.env. - Tests authenticate, plus new coverage: /app/ redirects when logged out, login grants access, /api/ is not caught by the app gate. Co-Authored-By: Claude Opus 4.8

Migrate dependency management to uv

2026-06-23T18:55:42+00:00

Replace requirements.txt with pyproject.toml (direct deps only; uv resolves the rest into uv.lock). Point the systemd unit at the uv-managed .venv, and gitignore it. Run `uv lock` to generate the lockfile and commit it. Co-Authored-By: Claude Opus 4.8

Phase 4: HTMX frontend with dark palette

2026-04-02T22:08:43+00:00

- 4 pages: Pantry, Recipes, Shopping List, Cook Log - HTMX-powered: add/delete pantry items, toggle shopping, generate smart list - Custom 13-colour palette from Lospec (dark bg, yellow accent) - Mobile-responsive - Whitenoise for static files in production - All routes under /app/ - API (/api/) stays internal, frontend (/app/) for browser use