Skip to content

Latest commit

 

History

History
51 lines (43 loc) · 1.94 KB

File metadata and controls

51 lines (43 loc) · 1.94 KB

NodeHub Rewrite Plan

Product direction

NodeHub is being rewritten from a simple node CRUD/subscription generator into a modern self-hosted proxy node asset hub:

Sources / Manual Import → Normalized Proxy Library → Tags & Smart Filters → Profile Pipeline → Client-specific Subscription Output

MVP scope for rewrite

Backend

  • Keep FastAPI + SQLite for easy self-hosting.
  • Replace flat group-centric logic with modern resources:
    • sources: upstream subscription URLs and sync status.
    • proxies: normalized proxy assets.
    • tags: many-to-many node labels.
    • profiles: public subscription outputs.
    • tasks: sync/test/export jobs and audit trail.
  • Add compatibility routes for current clients where useful.
  • Add batch import preview/sync primitives.
  • Add access logs and profile tokens.

Frontend

  • Replace single HTML file with React + Vite app.
  • UI structure:
    • Dashboard
    • Proxy Library
    • Sources
    • Profiles
    • Tasks & Logs
    • Settings/Admin
  • Modern control-panel design:
    • Dark-first theme with light toggle.
    • Sidebar + top command/action bar.
    • KPI cards, status badges, drawers/modals, toasts.
    • Dense but readable data tables.
    • Copy buttons, QR codes, token masking.

Important product behavior

  • Profiles explicitly choose client format instead of only UA guessing.
  • Nodes can have multiple tags; profiles select by tags/protocols/search conditions.
  • Batch operations: tag, test, export, delete.
  • Health status is first-class: latency, last tested, error.
  • Sources remember origin and sync failures.

Implementation phases

  1. Foundation: FastAPI modular rewrite + SQLite schema + React app shell.
  2. Core flows: auth, dashboard, proxy library, import, tags, profiles, subscription output.
  3. Operational flows: sources sync, tasks/logs, admin settings, backup/restore.
  4. Verification: local API tests, frontend build, Docker build, browser validation.
  5. Push to GitHub and update knowledge base.