e21a26db18
Widget: - Fetches /api/fitness/entries/totals and /api/fitness/goals/for-date directly from gateway using shared session cookie - Falls back to cached data in App Group UserDefaults if network fails - Refreshes every 15 minutes via WidgetKit timeline - Each phone shows the logged-in user's own data Auth sharing: - AuthManager.syncCookieToWidget() copies the session cookie to App Group UserDefaults on login and auth check - Widget reads cookie and makes authenticated API calls - Logout clears widget auth + cached data Data in App Group (group.com.quadjourney.platform): - widget_sessionCookie: auth token for API calls - widget_totalCalories: cached fallback - widget_calorieGoal: cached fallback - widget_lastUpdate: cache timestamp HomeViewModel also writes cache on each loadTodayData() as fallback. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Gitea CI Workflows
security.yml
Runs on push/PR to master. Three jobs:
- dependency-audit —
npm audit --audit-level=highfor budget and frontend - secret-scanning — checks for tracked .env/.db files and hardcoded secret patterns
- dockerfile-lint — verifies all Dockerfiles have
USER(non-root) andHEALTHCHECK
Runner Setup
The runner is configured in the Gitea docker-compose at /media/yusiboyz/Media/Scripts/gitea/docker-compose.yml.
What was done:
- Added
[actions] ENABLED = trueto Gitea'sapp.ini - Added
runnerservice (gitea/act_runner) to Gitea's docker-compose - Generated runner token via
docker exec -u git gitea gitea actions generate-runner-token - Token stored in
/media/yusiboyz/Media/Scripts/gitea/.envasRUNNER_TOKEN - Runner registered as
platform-runnerwith labels: ubuntu-latest, ubuntu-24.04, ubuntu-22.04
To regenerate token (if needed):
cd /media/yusiboyz/Media/Scripts/gitea
docker exec -u git gitea gitea actions generate-runner-token
# Update .env with new RUNNER_TOKEN value
docker compose up -d runner
To check runner status:
docker logs gitea-runner