mirror of https://github.com/MHSanaei/3x-ui.git synced 2026-05-15 10:36:30 +00:00

History

MHSanaei 3f16b661ac feat(frontend): Phase 6-iv — xray Outbounds tab + outbound modal Replaces the Outbounds tab placeholder with a full table + add/edit flow. The 1.3k-line legacy outbound modal is condensed to a tabbed modal with structured Basics fields (tag/protocol/sendThrough/domain strategy) and JSON tabs for the protocol-specific settings + stream trees — same approach the Inbound modal uses, and a power user can still edit the same trees via the page-level Advanced (JSON) tab. - useXraySetting.js: adds fetchOutboundsTraffic + resetOutboundsTraffic + testOutbound. Test states are tracked per outbound index so the row's Test button can show loading + the Test-result column can render the response delay / status / error. - OutboundsTab.vue: full table (action / identity / address / traffic / test result / test) plus a card-list mobile variant with the same row dropdown (set-first / edit / move up/down / reset traffic / delete). outboundAddresses() reproduces the legacy findOutboundAddress logic so each protocol's host:port list is rendered consistently. Add/edit go through OutboundFormModal, delete goes through Modal.confirm, reset traffic posts to /panel/xray/resetOutboundsTraffic with the row's tag (or "-alltags-" from the toolbar). - OutboundFormModal.vue: tag/protocol/sendThrough/domainStrategy on the Basics tab; settings + streamSettings as raw JSON on their respective tabs. Tag-collision check happens client-side before emitting; malformed JSON aborts the save with a message.error. - XrayPage.vue: imports OutboundsTab and wires the test action to the composable's testOutbound helper. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>		2026-05-08 14:27:40 +02:00
..
src	feat(frontend): Phase 6-iv — xray Outbounds tab + outbound modal	2026-05-08 14:27:40 +02:00
.gitignore	build(frontend): Phase 2 — scaffold Vite + Vue 3 + AD-Vue 4	2026-05-08 10:36:03 +02:00
inbounds.html	feat(frontend): Phase 5f-i — inbounds page shell + list fetch	2026-05-08 13:28:15 +02:00
index.html	feat(frontend): Phase 5c-i — index.html dashboard shell	2026-05-08 12:26:51 +02:00
login.html	feat(frontend): Phase 5a — theme system + Vite 8 + vue-i18n 11	2026-05-08 11:11:06 +02:00
package-lock.json	feat(frontend): Phase 5f-iii — inbound add/edit modal + delete/clone/reset	2026-05-08 13:41:21 +02:00
package.json	feat(frontend): Phase 5f-iii — inbound add/edit modal + delete/clone/reset	2026-05-08 13:41:21 +02:00
README.md	build(frontend): Phase 2 — scaffold Vite + Vue 3 + AD-Vue 4	2026-05-08 10:36:03 +02:00
settings.html	feat(frontend): Phase 5d-i — settings page shell + dirty tracking	2026-05-08 13:04:06 +02:00
vite.config.js	feat(frontend): Phase 6-i — xray page scaffold + Advanced JSON tab	2026-05-08 14:13:26 +02:00
xray.html	feat(frontend): Phase 6-i — xray page scaffold + Advanced JSON tab	2026-05-08 14:13:26 +02:00

README.md

3x-ui frontend

Vue 3 + Ant Design Vue 4 + Vite. Builds into ../web/dist/, which the Go binary will embed via embed.FS once the migration reaches the page handlers (Phase 4+).

This directory exists alongside the legacy web/html/ Vue 2 templates during the migration. Pages will move over one at a time on the vue3-migration branch.

Dev

cd frontend
npm install
npm run dev

The dev server runs on http://localhost:5173/ and proxies API calls to the Go panel at http://localhost:2053/ — start the Go panel first (go run main.go), then start Vite.

Production build

npm run build

Outputs to ../web/dist/. The Go binary picks it up at compile time via embed.FS.

Where things live

src/main.js — app entrypoint (createApp, install Antd, mount)
src/App.vue — root component (currently a smoke-test placeholder)
vite.config.js — build + dev-server config
index.html — Vite HTML template

Adding new pages

For each legacy page being migrated, add an entry to vite.config.js rollupOptions.input. Each entry produces its own HTML file in web/dist/, which the Go panel route handler will serve.