bcd2d96a1f
- add site-settings singleton to admin registry + schema + migration - add editor config + route + nav in admin frontend - surface defaultSiteTheme via data-api serialize + shared types + validator - carry through api /www/provider-config (the public edge-cached path on vps0) - remove DEFAULT_SITE_THEME hardcode; ultimate fallback luxe-dark; registry comments updated for admin-driven live selector - live bootstrap in quinn.www root + data hook to pick admin default without quinn.www rebuild (chrome + tokens update post-fetch) - fixed incidental sortable test assertion to match current registry (pre-existing mismatch) - other public hardcodes remain in deployment configs; see analysis This makes the visitor-facing default theme choice Quinn-editable via admin UI and flows as public data through the quinn.api public surface (edge cacheable). |
||
|---|---|---|
| .. | ||
| migrations | ||
| src | ||
| .env.development | ||
| .env.local.example | ||
| package.json | ||
| README.md | ||
| tsconfig.json | ||
| vitest.config.ts | ||
Admin API
Node.js HTTP server for the Quinn admin control center. Port 3023.
Auth: SSO cookie (via quinn-sso-api) or service bearer token (QUINN_ADMIN_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_ADMIN_SERVICE_TOKEN>. No local SQLite is touched.
Copy .env.local.example to .env.local and fill in the token:
cp .env.local.example .env.local
# edit .env.local — get QUINN_ADMIN_SERVICE_TOKEN from /etc/quinn-admin-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.