Telegram-Market/telegram-shop
1
1
Fork 0
Code Issues 40 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

Создать API для управления настройками бота (Settings API) #93

New Issue
Open
opened 2026-06-17 19:43:21 +00:00 by NW · 0 comments
NW commented 2026-06-17 19:43:21 +00:00
Owner
Copy Link

Описание

API для управления настройками через веб-интерфейс: BOT_TOKEN, ADMIN_IDS, кошельки, WireGuard, и т.д.

Задачи

  • Таблица settings (key, value, type, description, updated_at)
  • src/admin/routes/settings.js — CRUD
  • src/admin/services/settingsService.js
  • Миграция: импорт env vars → settings DB
  • Приоритет: settings DB > .env > default
  • Шифрование секретных значений (BOT_TOKEN, ENCRYPTION_KEY, WG_PRIVATE_KEY)
  • Маскирование секретов в GET-ответах

Настройки: BOT_TOKEN, ADMIN_IDS, SUPPORT_LINK, COMMISSION_, WG_, ENCRYPTION_KEY, LOG_LEVEL

Приоритет: ВЫСОКИЙ

## Описание API для управления настройками через веб-интерфейс: BOT_TOKEN, ADMIN_IDS, кошельки, WireGuard, и т.д. ## Задачи - [ ] Таблица `settings` (key, value, type, description, updated_at) - [ ] `src/admin/routes/settings.js` — CRUD - [ ] `src/admin/services/settingsService.js` - [ ] Миграция: импорт env vars → settings DB - [ ] Приоритет: settings DB > .env > default - [ ] Шифрование секретных значений (BOT_TOKEN, ENCRYPTION_KEY, WG_PRIVATE_KEY) - [ ] Маскирование секретов в GET-ответах ## Настройки: BOT_TOKEN, ADMIN_IDS, SUPPORT_LINK, COMMISSION_*, WG_*, ENCRYPTION_KEY, LOG_LEVEL ## Приоритет: ВЫСОКИЙ
NW added this to the Phase 3: Admin Panel Foundation milestone 2026-06-17 19:43:21 +00:00
NW added the priority::hightype::featurephase::3 labels 2026-06-17 19:43:21 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
phase::1
Phase 1: Security
 phase::1
Phase 1
 phase::1
Phase 1
 phase::2
Phase 2: Architecture
 phase::2
Phase 2
 phase::3
Phase 3: Admin API
 phase::3
Phase 3
 phase::4
Phase 4: Web UI
 phase::4
Phase 4
 phase::5
Phase 5: Quality
 phase::5
Phase 5
 priority::critical
Critical priority
 priority::critical
Critical priority
 priority::high
High priority
 priority::high
High priority
 priority::medium
Medium priority
 priority::medium
Medium priority
 type::bug
Bug fix
 type::bug
Bug
 type::feature
New feature
 type::feature
Feature
 type::infra
Infrastructure
 type::infra
Infrastructure
 type::refactor
Code refactoring
 type::refactor
Refactoring
 type::security
Security issue
 type::security
Security
 type::testing
Testing
 type::testing
Testing
No Label phase::3 priority::high type::feature
Milestone
No items
No Milestone Phase 3: Admin Panel Foundation
Projects
Clear projects
No project
Assignees
Clear assignees
NW
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Telegram-Market/telegram-shop#93
Delete Branch "%!s()"

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?