23 lines
1.1 KiB
Markdown
23 lines
1.1 KiB
Markdown
# Plan
|
|
|
|
Updated: 2026-04-01
|
|
|
|
## Active
|
|
|
|
1. Present the UI-first slice for approval, then replace mocks with runtime-backed 3proxy control flows.
|
|
|
|
## Next
|
|
|
|
1. Replace mocks with a backend control plane for config generation, process management, counters, and health checks.
|
|
2. Add Docker runtime with 3proxy, panel server, health checks, and reload/start/restart operations.
|
|
3. Extend tests to cover config rendering, unsafe input handling, and runtime failure scenarios.
|
|
|
|
## Done
|
|
|
|
1. Researched official 3proxy documentation for config scripting, services, counters, reports, auth, and reload hooks.
|
|
2. Initialized the repository and established autonomous agent workflow rules.
|
|
3. Implemented the first UI slice with hardcoded panel auth, operator-focused dashboard, users table, and system config preview.
|
|
4. Added paranoia-oriented tests for login gating, proxy link encoding, quota edge cases, and traffic share formatting.
|
|
5. Simplified the UI into a calmer minimalist layout with reduced visual noise and denser operational presentation.
|
|
6. Moved user creation into a modal flow and tightened the operator UX with quieter navigation and a denser users table.
|