controlPanel/api
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: new.gholaktala.ir is Khanegi modular, not Hamkar

Browse Source 
Revert wrong FORCE_HAMKAR classification; lock domain in FORCE_KHANEGI and keep Hamkar/Khanegi overrides separate.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
Mahdi
2026-08-11 17:40:13 +03:30
co-authored by Cursor
parent 0aeb17bd1b
commit 859530a669
3 changed files with 120 additions and 118 deletions
Download Patch File Download Diff File Expand all files Collapse all files
prisma/import-users.ts
+3 -4
View File
@@ -30,15 +30,14 @@ const FORCE_KHANEGI: Array<{ domain?: string; name?: string; externalId?: number
{ domain: 'abaeigold.ir' },
{ domain: 'niazitala.ir' },
{ domain: 'garoosigholaktala.ir' },
{ domain: 'new.gholaktala.ir' },
{ domain: 'kh.kashkolgold.ir' },
{ domain: 'goldsun.zaarbox.ir' },
{ domain: 'goldaliii.com' },
];
/** Never mix with FORCE_KHANEGI — these sold versions are Hamkar (site/* APIs). */
const FORCE_HAMKAR: Array<{ domain?: string; name?: string; externalId?: number }> = [
{ domain: 'new.gholaktala.ir' },
];
/** Manual Hamkar locks — never put Khanegi domains here. */
const FORCE_HAMKAR: Array<{ domain?: string; name?: string; externalId?: number }> = [];
/** Canonical public domains after migrations */
const DOMAIN_OVERRIDES: Record<string, { domain: string; appUrl: string; nodeServer: string }> = {