lilith-platform.live/codebase/@features/my/backend-api
2026-06-08 01:38:46 -07:00
..
scripts feat(events): Add seed and verification scripts for events expansion, along with comprehensive test coverage 2026-06-03 08:00:28 -07:00
src docs(backend-api): 📝 Clarify test documentation to distinguish between local and proxied operations in projects routes 2026-06-08 01:38:46 -07:00
.env.development chore(backend-api): 🔧 Update development environment variables in .env.development 2026-05-14 18:56:09 -07:00
.env.local.example
eslint.config.js
package.json deps-upgrade(backend-api): ⬆️ Update dependencies across backend-api, admin, and price-watcher packages 2026-04-24 20:04:56 -07:00
README.md
tsconfig.json
vitest.config.ts chore(backend-api): 🔧 Update dev env vars, Vitest config, and deployment examples for backend API 2026-06-08 00:10:31 -07:00

My Dashboard API

Node.js HTTP server for the Quinn personal dashboard. Port 3024.

Auth: SSO cookie (via quinn-sso-api) or service bearer token (QUINN_MY_SERVICE_TOKEN).

Dev proxy mode

When PROXY_TARGET is set, the server short-circuits every request (except /health) and proxies it upstream to the target, injecting Authorization: Bearer <QUINN_MY_SERVICE_TOKEN>. No local SQLite is touched. SSE streams (calendar sync etc.) pass through transparently — the response body is streamed, not buffered.

Copy .env.local.example to .env.local and fill in the token:

cp .env.local.example .env.local
# edit .env.local — get QUINN_MY_SERVICE_TOKEN from /etc/quinn-my-api/secrets.env on vps-0

The server logs a WARN line at boot when proxy mode is active, and prefixes each proxied request log with [PROXY→prod].

See docs/PROD_DB_UNIFICATION_PLAN.md for full architecture context.