The integration was half-committed: server.ts imported ./ma7 and the profile tab was documented, but neither file ever reached the repository, so awg-ui could not start at all — `Error: Cannot find module './ma7'`. Everything that referenced it is gone: the import and the /ui/ma7/profile route, the three MA7_* variables the CLI passed to awg-ui, the installer prompts and their cli.env block, and the README section. The panel login prompt goes back to defaulting to admin instead of the MA7 subscriber login. awg-ui type-checks, builds and starts again.
This commit is contained in:
@@ -90,13 +90,6 @@ const SERVICES = {
|
||||
UI_USER: process.env.UI_USER ?? "admin",
|
||||
UI_PASS: process.env.UI_PASS ?? "",
|
||||
JWT_SECRET: process.env.JWT_SECRET ?? "",
|
||||
// Интеграция с API MA7 (см. awg-ui/ma7.ts) — секрет чужого сервиса,
|
||||
// не совпадает с UI_* / JWT_SECRET этой панели. MA7_LOGIN — логин
|
||||
// владельца этого персонального сервера в MA7 ('ma7_xxxxxx'):
|
||||
// задаётся один раз при установке, в панели не редактируется.
|
||||
MA7_API_BASE_URL: process.env.MA7_API_BASE_URL ?? "",
|
||||
MA7_JWT_SECRET: process.env.MA7_JWT_SECRET ?? "",
|
||||
MA7_LOGIN: process.env.MA7_LOGIN ?? "",
|
||||
},
|
||||
pidFile: "/tmp/awg-ui.pid",
|
||||
logFile: path.join(LOGS, "awg-ui.log"),
|
||||
|
||||
Reference in New Issue
Block a user