dokril/harbor-net
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 2 Wiki Activity

Clarify active Windows client architecture

Browse Source
This commit is contained in:
Dokril
2026-07-07 21:19:41 +03:00
parent a0f41baa36
commit 59f2264a2e
55 changed files with 19554 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/superpowers/specs/2026-05-21-windows-client-design.md
View File

@@ -1,5 +1,12 @@
# Windows Client Design
> Superseded: this document describes the earlier Node/web-control Windows direction.
> The active Windows direction is a standalone Tauri 2 desktop app under
> `apps/windows-client`, driven by `docs/windows-client-product-tech-brief.md`
> and `docs/goals/windows-modular-client/PLAN.md`.
> Content below is retained for historical context and may contradict the active
> Tauri plan.
## Goal
Restore the old Windows workflow in a cleaner product shape: a one-command PowerShell installer can install either a full local `sing-box` + ProxiFyre setup or ProxiFyre-only routing to an existing proxy, then expose a small local web UI for profiles, folders, executable files, status, and logs.