Mirror the api/sso build stamp on quinn-my-api: inject __BUILD_INFO__ via bun build --define in deploy.sh and return version/buildCount/sha/builtAt + service + startedAt as JSON from /health (was bare 'ok'). Falls back to env then 'dev'. |
||
|---|---|---|
| .. | ||
| scripts | ||
| src | ||
| .env.development | ||
| .env.local.example | ||
| eslint.config.js | ||
| package.json | ||
| README.md | ||
| tsconfig.json | ||
| vitest.config.ts | ||
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.