feat(settings): store Khanegi keys in settings tables instead of tenant JSON

Browse Source

Template defaults seed from deploy_settings_const; new tenants copy them, import decides per key, and /get_settings reads the per-tenant rows.

Co-authored-by: Cursor <cursoragent@cursor.com>

...

This commit is contained in:

mohmdsdg

2026-08-17 20:14:17 +03:30

co-authored by Cursor

parent 8f9988eb15

commit d57ce0a3cb

15 changed files with 2659 additions and 354 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

src/program-settings/program-settings.service.ts

+585 -273

File diff suppressed because it is too large Load Diff