feat(settings): instance settings + preferences pane #18
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/settings-pane"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
preferences(user_id, key, value, updated_at)andinstance_settings(key, value, updated_at)SETTINGSregistry is the single source of truth; instance settings follow env > db > default precedence with a "set by env" badge in the UI when an env var winsPOST /api/auth/rotate-passphrase) re-encrypts all connection tokens atomically in a single transaction, destroys all existing sessions, and issues a fresh cookieSessionStoreTTL is now read lazily — changingsession_ttl_hoursin the UI takes effect on next login without a restartGIT_USER_NAME/GIT_USER_EMAILfrom preferences andworker_imagefrom instance settings instead of hardcoded configdefault_agent_teams_enabledpreference on mountTest plan
pnpm testinnexus/— 246 passing, 65 skipped (SQLite skipped on Windows, run on Linux/CI)pnpm typecheck— 0 errorsdocker compose up -d --build/settings→ Preferences tab: change git name → save → toast appears, value persists on refreshWORKER_IMAGEenv var in compose → restart → field shows "set by env" chip, input is replaced by chipf5026396a9f2dc07f6c2f2dc07f6c2e904410f72e904410f728142e46feflz referenced this pull request2026-05-28 01:15:54 +02:00
lz referenced this pull request2026-05-28 22:20:13 +02:00