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

History

MHSanaei bb74e425fe feat(frontend): Phase 5f-v — inbound info + QR-code modals Wires the row "info" and "qrcode" actions and ports the legacy inbound_info_modal end-to-end. The info modal handles every protocol the legacy panel did: • multi-user (VMess/VLess/Trojan/SS-multi/Hysteria) — per-client table + share links + per-link QR; • SS single-user — share link + QR; • WireGuard — full peer table with downloadable peer-N.conf and a wg:// share link per peer; • Mixed/HTTP/Tunnel — connection-detail tables. - QrPanel.vue: shared link card (header tag, copy button, optional download button, optional QR canvas, monospace footer with the raw value). Per-instance QRious instances are repainted on value/size change. - InboundInfoModal.vue: full info modal. Subscription URL block keys off subSettings.subURI/subJsonURI; IP-log lazy-loads on open and surfaces refresh + clear; tg-id, last-online, depleted/enabled tags all match legacy. - QrCodeModal.vue: lighter modal used for the row "qrcode" action on SS-single and WireGuard inbounds (just the QRs, no info table). - InboundsPage.vue: wires both flows. checkFallback() reproduces the legacy logic — when an inbound listens on a unix-socket fallback (`@<name>`), the link generator is pointed at the root inbound that owns the listen address so QRs/links carry the public host:port + the right TLS state. Multi-client navigation (focusing a specific client's links) is deferred to 5f-vi where the per-inbound expand- row table will pass the email through. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>		2026-05-08 13:52:45 +02:00
..
src	feat(frontend): Phase 5f-v — inbound info + QR-code modals	2026-05-08 13:52:45 +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 5f-i — inbounds page shell + list fetch	2026-05-08 13:28:15 +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.