okooooooo/3m-ui
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
1,133 Commits 1 Branch 0 Tags
main
Commit Graph
6 Commits
Author SHA1 Message Date
風雪 c6cf289228 fix(scripts): make SSH menu config access indentation-agnostic (#101) 
* fix(scripts): make SSH menu config access indentation-agnostic

Running the panel built from source exposed two defects that static review
could not see, because both depend on what the Go binary actually writes to
config.yaml.

The Go binary rewrites config.yaml through a YAML marshaller. `init` emits
two-space indentation, but any later rewrite — notably `reset-config`, the SSH
rescue path — emits four, and re-sorts the keys. Every shell helper matched on
a hardcoded two-space prefix, so the menu and the binary disagreed about the
file's shape.

1. Duplicate keys after an SSH rescue

After `reset-config`, `yaml_get '  port:'` matched nothing, so the menu showed
an empty current port. `yaml_set` then took its insert branch and appended a
two-space `port:` line alongside the marshaller's four-space one:

    server:
        mode: release
        port: 8080
        sub_port: 0
      port: 9090          <- inserted, duplicate

The menu then reported "Configured port: 9090" and restarted the service. The
failure mode matters more than the diff: SSH rescue is what an operator reaches
for when the panel is unreachable, which is exactly when the menu has to work.

2. `3m-ui config port <port>` left the panel unable to boot

That command hardcoded a two-space indent, producing mixed indentation inside
one block:

    server:
        mode: release
      port: 19090
        public_url: ""

The binary then refuses to start at all:

    failed to decode config YAML: yaml: line 12: did not find expected key

This command is documented in the README, so following the documentation
bricks the panel.

Both are fixed the same way: key lookup is now indentation-agnostic (matched
on $1 rather than a fixed prefix, which also removes any ambiguity between
`port:` and `sub_port:`), replacement preserves the indentation of the line it
rewrites, and insertion adopts the block's existing indent. Callers pass
"port:" instead of "  port:".

Also fixed: menu item 17 (Healthcheck) produced no output at all, because the
binary's healthcheck exits 0 silently on success. It now reports pass/fail
based on the exit status.

Verified against a panel compiled from source and running on loopback:
rescue -> change port -> restart yields a single `port:` key with consistent
indentation, config stays 0600, the panel serves HTTP 200, and the healthcheck
item reports OK. The regression script (scripts regression, 16 cases) covers
both defects by reproducing them against the old implementation first.

* fix(scripts): make SSH menu config access indentation-agnostic

Running the panel built from source exposed two defects that static review
could not see, because both depend on what the Go binary actually writes to
config.yaml.

The Go binary rewrites config.yaml through a YAML marshaller. `init` emits
two-space indentation, but any later rewrite — notably `reset-config`, the SSH
rescue path — emits four, and re-sorts the keys. Every shell helper matched on
a hardcoded two-space prefix, so the menu and the binary disagreed about the
file's shape.

1. Duplicate keys after an SSH rescue

After `reset-config`, `yaml_get '  port:'` matched nothing, so the menu showed
an empty current port. `yaml_set` then took its insert branch and appended a
two-space `port:` line alongside the marshaller's four-space one:

    server:
        mode: release
        port: 8080
        sub_port: 0
      port: 9090          <- inserted, duplicate

The menu then reported "Configured port: 9090" and restarted the service. The
failure mode matters more than the diff: SSH rescue is what an operator reaches
for when the panel is unreachable, which is exactly when the menu has to work.

2. `3m-ui config port <port>` left the panel unable to boot

That command hardcoded a two-space indent, producing mixed indentation inside
one block:

    server:
        mode: release
      port: 19090
        public_url: ""

The binary then refuses to start at all:

    failed to decode config YAML: yaml: line 12: did not find expected key

This command is documented in the README, so following the documentation
bricks the panel.

Both are fixed the same way: key lookup is now indentation-agnostic (matched
on $1 rather than a fixed prefix, which also removes any ambiguity between
`port:` and `sub_port:`), replacement preserves the indentation of the line it
rewrites, and insertion adopts the block's existing indent. Callers pass
"port:" instead of "  port:".

Also fixed: menu item 17 (Healthcheck) produced no output at all, because the
binary's healthcheck exits 0 silently on success. It now reports pass/fail
based on the exit status.

Verified against a panel compiled from source and running on loopback:
rescue -> change port -> restart yields a single `port:` key with consistent
indentation, config stays 0600, the panel serves HTTP 200, and the healthcheck
item reports OK. The regression script (scripts regression, 16 cases) covers
both defects by reproducing them against the old implementation first.

* test(scripts): add regression coverage for the SSH menu config helpers

The existing lifecycle tests exercise install.sh end to end but never touch
the menu's config read/write path, which is where both defects in the previous
commit lived. This adds 16 cases.

Each case runs the pre-fix implementation and the fixed one against the same
input and asserts both directions: the old one must reproduce the defect, the
new one must not exhibit it. A case whose "before" assertion passes is scored
FAIL — otherwise the suite could go green without ever having exercised the
bug.

Covers: block-scoped writes, 0600 preservation, `config port` with a missing
argument, the self-referencing entrypoint loop, insertion placement, missing
`server:` block, indentation-agnostic lookup, and indentation consistency.

The suite is self-contained: it needs no installed panel, writes only to a
temp dir, and the one case that touches /usr/local/bin/3m-ui skips itself if
that path already exists.
 2026-10-09 00:39:10 +08:00
風雪 84eab7750c fix(scripts): scope SSH menu config writes to the server: block (#100) 
* fix(scripts): scope SSH menu config writes to the server: block

The SSH management menu edited /etc/3m-ui/config.yaml with a global sed
substitution, which rewrote every identically-indented key in the file rather
than just the panel's. Changing the panel port therefore also rewrote unrelated
listener ports, and because the menu restarts the service right afterwards the
corruption went live immediately.

The same code path wrote the new file with `mv`, so a 0600 config holding the
JWT and credential-encryption keys came back as a umask-default 0644 file,
readable by every local user after any port or path change.

Both are fixed by scoping reads/writes to the `server:` block and by writing
back through the original inode (`cat > file`) instead of replacing it.

Three further defects found while auditing the menu:

- scripts/3m-ui.sh: `config port` read a bare "$2" under `set -u`, so running
  it without an argument aborted with "parameter not set" and the usage
  message below it was unreachable. Now "${2:-}".
- scripts/3m-ui.sh: the no-arg branch exec'd /usr/local/bin/3m-ui without
  checking whether it resolves back to this script, which spun in an endless
  exec loop on a broken entrypoint. Direct and indirect self-reference are now
  detected and reported with an actionable message.
- scripts/3m-ui: `enable_bbr` wrote into /etc/sysctl.d without creating it; on
  minimal/container images the redirect failed and `set -e` tore down the whole
  interactive menu. Now mkdir -p with a guarded failure.

Hardening and consistency:

- yaml_set reports an error instead of silently no-oping when neither the key
  nor a `server:` block exists; the menu no longer restarts the service for a
  change that never happened.
- yaml_get is scoped to the `server:` block so it matches yaml_set.
- temp files come from mktemp (0600) instead of a predictable .$$ name.
- open_firewall asks for confirmation before opening 22/80/443.
- status reports boot-time enablement on OpenRC, not only systemd.
- menu item 8 reports invalid input instead of returning silently.
- menu item 23 is relabelled: it updates all of 3m-ui, not only the script.
- the acme.sh helper is annotated as an example to review before running.

Verified locally: the listener port is left untouched when the panel port
changes, config mode stays 0600, `config port` with no argument prints usage,
the self-referencing entrypoint fails fast instead of looping, and both files
pass `sh -n`.

* fix(scripts): scope SSH menu config writes to the server: block

The SSH management menu edited /etc/3m-ui/config.yaml with a global sed
substitution, which rewrote every identically-indented key in the file rather
than just the panel's. Changing the panel port therefore also rewrote unrelated
listener ports, and because the menu restarts the service right afterwards the
corruption went live immediately.

The same code path wrote the new file with `mv`, so a 0600 config holding the
JWT and credential-encryption keys came back as a umask-default 0644 file,
readable by every local user after any port or path change.

Both are fixed by scoping reads/writes to the `server:` block and by writing
back through the original inode (`cat > file`) instead of replacing it.

Three further defects found while auditing the menu:

- scripts/3m-ui.sh: `config port` read a bare "$2" under `set -u`, so running
  it without an argument aborted with "parameter not set" and the usage
  message below it was unreachable. Now "${2:-}".
- scripts/3m-ui.sh: the no-arg branch exec'd /usr/local/bin/3m-ui without
  checking whether it resolves back to this script, which spun in an endless
  exec loop on a broken entrypoint. Direct and indirect self-reference are now
  detected and reported with an actionable message.
- scripts/3m-ui: `enable_bbr` wrote into /etc/sysctl.d without creating it; on
  minimal/container images the redirect failed and `set -e` tore down the whole
  interactive menu. Now mkdir -p with a guarded failure.

Hardening and consistency:

- yaml_set reports an error instead of silently no-oping when neither the key
  nor a `server:` block exists; the menu no longer restarts the service for a
  change that never happened.
- yaml_get is scoped to the `server:` block so it matches yaml_set.
- temp files come from mktemp (0600) instead of a predictable .$$ name.
- open_firewall asks for confirmation before opening 22/80/443.
- status reports boot-time enablement on OpenRC, not only systemd.
- menu item 8 reports invalid input instead of returning silently.
- menu item 23 is relabelled: it updates all of 3m-ui, not only the script.
- the acme.sh helper is annotated as an example to review before running.

Verified locally: the listener port is left untouched when the panel port
changes, config mode stays 0600, `config port` with no argument prints usage,
the self-referencing entrypoint fails fast instead of looping, and both files
pass `sh -n`.
 2026-10-08 23:49:39 +08:00
Z User 00249cd168 feat(scripts): wire reset-config into 3m-ui CLI wrapper + install hint 
The new '3m-ui reset-config' Go subcommand (commit 8639b01) lets SSH
operators undo panel misconfigurations (wrong port / 127.0.0.1 bind /
broken SSL). This change exposes it through the systemd management
wrapper and documents it in the install banner.
scripts/3m-ui.sh:
- Add 'reset_config' function: stops the panel service (required by
the Go binary since it writes config.yaml + DB rows the running
panel might cache), invokes 3m-ui-bin reset-config <flags>, then
restarts the panel.
- --help / -h short-circuits the stop/restart cycle (read-only).
- Add 'reset-config' to the main case dispatch.
- Document the new subcommand + flags in usage() with examples.
scripts/install.sh:
- Append a line to the post-install banner pointing operators at
'3m-ui reset-config --panel --yes' for SSH rescue scenarios.
USAGE
sudo 3m-ui reset-config                       # interactive y/N, panel scope
sudo 3m-ui reset-config --panel --yes        # scripted rescue (common case)
sudo 3m-ui reset-config --all --yes          # full reset
sudo 3m-ui reset-config --help               # full help (no service touched)
Smoke-tested with a fake binary: dispatch + flag passthrough + env vars
all correct; --help does not stop the service.
feat(scripts): wire reset-config into 3m-ui CLI wrapper + install hint
The new '3m-ui reset-config' Go subcommand (commit 8639b01) lets SSH
operators undo panel misconfigurations (wrong port / 127.0.0.1 bind /
broken SSL). This change exposes it through the systemd management
wrapper and documents it in the install banner.
scripts/3m-ui.sh:
- Add 'reset_config' function: stops the panel service (required by
the Go binary since it writes config.yaml + DB rows the running
panel might cache), invokes 3m-ui-bin reset-config <flags>, then
restarts the panel.
- --help / -h short-circuits the stop/restart cycle (read-only).
- Add 'reset-config' to the main case dispatch.
- Document the new subcommand + flags in usage() with examples.
scripts/install.sh:
- Append a line to the post-install banner pointing operators at
'3m-ui reset-config --panel --yes' for SSH rescue scenarios.
USAGE
sudo 3m-ui reset-config                       # interactive y/N, panel scope
sudo 3m-ui reset-config --panel --yes        # scripted rescue (common case)
sudo 3m-ui reset-config --all --yes          # full reset
sudo 3m-ui reset-config --help               # full help (no service touched)
Smoke-tested with a fake binary: dispatch + flag passthrough + env vars
all correct; --help does not stop the service.
feat(scripts): wire reset-config into 3m-ui CLI wrapper + install hint
The new '3m-ui reset-config' Go subcommand (commit 8639b01) lets SSH
operators undo panel misconfigurations (wrong port / 127.0.0.1 bind /
broken SSL). This change exposes it through the systemd management
wrapper and documents it in the install banner.
scripts/3m-ui.sh:
- Add 'reset_config' function: stops the panel service (required by
the Go binary since it writes config.yaml + DB rows the running
panel might cache), invokes 3m-ui-bin reset-config <flags>, then
restarts the panel.
- --help / -h short-circuits the stop/restart cycle (read-only).
- Add 'reset-config' to the main case dispatch.
- Document the new subcommand + flags in usage() with examples.
scripts/install.sh:
- Append a line to the post-install banner pointing operators at
'3m-ui reset-config --panel --yes' for SSH rescue scenarios.
USAGE
sudo 3m-ui reset-config                       # interactive y/N, panel scope
sudo 3m-ui reset-config --panel --yes        # scripted rescue (common case)
sudo 3m-ui reset-config --all --yes          # full reset
sudo 3m-ui reset-config --help               # full help (no service touched)
Smoke-tested with a fake binary: dispatch + flag passthrough + env vars
all correct; --help does not stop the service.
feat(scripts): wire reset-config into 3m-ui CLI wrapper + install hint
The new '3m-ui reset-config' Go subcommand (commit 8639b01) lets SSH
operators undo panel misconfigurations (wrong port / 127.0.0.1 bind /
broken SSL). This change exposes it through the systemd management
wrapper and documents it in the install banner.
scripts/3m-ui.sh:
- Add 'reset_config' function: stops the panel service (required by
the Go binary since it writes config.yaml + DB rows the running
panel might cache), invokes 3m-ui-bin reset-config <flags>, then
restarts the panel.
- --help / -h short-circuits the stop/restart cycle (read-only).
- Add 'reset-config' to the main case dispatch.
- Document the new subcommand + flags in usage() with examples.
scripts/install.sh:
- Append a line to the post-install banner pointing operators at
'3m-ui reset-config --panel --yes' for SSH rescue scenarios.
USAGE
sudo 3m-ui reset-config                       # interactive y/N, panel scope
sudo 3m-ui reset-config --panel --yes        # scripted rescue (common case)
sudo 3m-ui reset-config --all --yes          # full reset
sudo 3m-ui reset-config --help               # full help (no service touched)
Smoke-tested with a fake binary: dispatch + flag passthrough + env vars
all correct; --help does not stop the service.
feat(scripts): wire reset-config into 3m-ui CLI wrapper + install hint
The new '3m-ui reset-config' Go subcommand (commit 8639b01) lets SSH
operators undo panel misconfigurations (wrong port / 127.0.0.1 bind /
broken SSL). This change exposes it through the systemd management
wrapper and documents it in the install banner.
scripts/3m-ui.sh:
- Add 'reset_config' function: stops the panel service (required by
the Go binary since it writes config.yaml + DB rows the running
panel might cache), invokes 3m-ui-bin reset-config <flags>, then
restarts the panel.
- --help / -h short-circuits the stop/restart cycle (read-only).
- Add 'reset-config' to the main case dispatch.
- Document the new subcommand + flags in usage() with examples.
scripts/install.sh:
- Append a line to the post-install banner pointing operators at
'3m-ui reset-config --panel --yes' for SSH rescue scenarios.
USAGE
sudo 3m-ui reset-config                       # interactive y/N, panel scope
sudo 3m-ui reset-config --panel --yes        # scripted rescue (common case)
sudo 3m-ui reset-config --all --yes          # full reset
sudo 3m-ui reset-config --help               # full help (no service touched)
Smoke-tested with a fake binary: dispatch + flag passthrough + env vars
all correct; --help does not stop the service.
feat(scripts): wire reset-config into 3m-ui CLI wrapper + install hint
The new '3m-ui reset-config' Go subcommand (commit 8639b01) lets SSH
operators undo panel misconfigurations (wrong port / 127.0.0.1 bind /
broken SSL). This change exposes it through the systemd management
wrapper and documents it in the install banner.
scripts/3m-ui.sh:
- Add 'reset_config' function: stops the panel service (required by
the Go binary since it writes config.yaml + DB rows the running
panel might cache), invokes 3m-ui-bin reset-config <flags>, then
restarts the panel.
- --help / -h short-circuits the stop/restart cycle (read-only).
- Add 'reset-config' to the main case dispatch.
- Document the new subcommand + flags in usage() with examples.
scripts/install.sh:
- Append a line to the post-install banner pointing operators at
'3m-ui reset-config --panel --yes' for SSH rescue scenarios.
USAGE
sudo 3m-ui reset-config                       # interactive y/N, panel scope
sudo 3m-ui reset-config --panel --yes        # scripted rescue (common case)
sudo 3m-ui reset-config --all --yes          # full reset
sudo 3m-ui reset-config --help               # full help (no service touched)
Smoke-tested with a fake binary: dispatch + flag passthrough + env vars
all correct; --help does not stop the service.
feat(scripts): wire reset-config into 3m-ui CLI wrapper + install hint
The new '3m-ui reset-config' Go subcommand (commit 8639b01) lets SSH
operators undo panel misconfigurations (wrong port / 127.0.0.1 bind /
broken SSL). This change exposes it through the systemd management
wrapper and documents it in the install banner.
scripts/3m-ui.sh:
- Add 'reset_config' function: stops the panel service (required by
the Go binary since it writes config.yaml + DB rows the running
panel might cache), invokes 3m-ui-bin reset-config <flags>, then
restarts the panel.
- --help / -h short-circuits the stop/restart cycle (read-only).
- Add 'reset-config' to the main case dispatch.
- Document the new subcommand + flags in usage() with examples.
scripts/install.sh:
- Append a line to the post-install banner pointing operators at
'3m-ui reset-config --panel --yes' for SSH rescue scenarios.
USAGE
sudo 3m-ui reset-config                       # interactive y/N, panel scope
sudo 3m-ui reset-config --panel --yes        # scripted rescue (common case)
sudo 3m-ui reset-config --all --yes          # full reset
sudo 3m-ui reset-config --help               # full help (no service touched)
Smoke-tested with a fake binary: dispatch + flag passthrough + env vars
all correct; --help does not stop the service.
feat(scripts): wire reset-config into 3m-ui CLI wrapper + install hint
The new '3m-ui reset-config' Go subcommand (commit 8639b01) lets SSH
operators undo panel misconfigurations (wrong port / 127.0.0.1 bind /
broken SSL). This change exposes it through the systemd management
wrapper and documents it in the install banner.
scripts/3m-ui.sh:
- Add 'reset_config' function: stops the panel service (required by
the Go binary since it writes config.yaml + DB rows the running
panel might cache), invokes 3m-ui-bin reset-config <flags>, then
restarts the panel.
- --help / -h short-circuits the stop/restart cycle (read-only).
- Add 'reset-config' to the main case dispatch.
- Document the new subcommand + flags in usage() with examples.
scripts/install.sh:
- Append a line to the post-install banner pointing operators at
'3m-ui reset-config --panel --yes' for SSH rescue scenarios.
USAGE
sudo 3m-ui reset-config                       # interactive y/N, panel scope
sudo 3m-ui reset-config --panel --yes        # scripted rescue (common case)
sudo 3m-ui reset-config --all --yes          # full reset
sudo 3m-ui reset-config --help               # full help (no service touched)
Smoke-tested with a fake binary: dispatch + flag passthrough + env vars
all correct; --help does not stop the service.
feat(scripts): wire reset-config into 3m-ui CLI wrapper + install hint
The new '3m-ui reset-config' Go subcommand (commit 8639b01) lets SSH
operators undo panel misconfigurations (wrong port / 127.0.0.1 bind /
broken SSL). This change exposes it through the systemd management
wrapper and documents it in the install banner.
scripts/3m-ui.sh:
- Add 'reset_config' function: stops the panel service (required by
the Go binary since it writes config.yaml + DB rows the running
panel might cache), invokes 3m-ui-bin reset-config <flags>, then
restarts the panel.
- --help / -h short-circuits the stop/restart cycle (read-only).
- Add 'reset-config' to the main case dispatch.
- Document the new subcommand + flags in usage() with examples.
scripts/install.sh:
- Append a line to the post-install banner pointing operators at
'3m-ui reset-config --panel --yes' for SSH rescue scenarios.
USAGE
sudo 3m-ui reset-config                       # interactive y/N, panel scope
sudo 3m-ui reset-config --panel --yes        # scripted rescue (common case)
sudo 3m-ui reset-config --all --yes          # full reset
sudo 3m-ui reset-config --help               # full help (no service touched)
Smoke-tested with a fake binary: dispatch + flag passthrough + env vars
all correct; --help does not stop the service.
feat(scripts): wire reset-config into 3m-ui CLI wrapper + install hint
The new '3m-ui reset-config' Go subcommand (commit 8639b01) lets SSH
operators undo panel misconfigurations (wrong port / 127.0.0.1 bind /
broken SSL). This change exposes it through the systemd management
wrapper and documents it in the install banner.
scripts/3m-ui.sh:
- Add 'reset_config' function: stops the panel service (required by
the Go binary since it writes config.yaml + DB rows the running
panel might cache), invokes 3m-ui-bin reset-config <flags>, then
restarts the panel.
- --help / -h short-circuits the stop/restart cycle (read-only).
- Add 'reset-config' to the main case dispatch.
- Document the new subcommand + flags in usage() with examples.
scripts/install.sh:
- Append a line to the post-install banner pointing operators at
'3m-ui reset-config --panel --yes' for SSH rescue scenarios.
USAGE
sudo 3m-ui reset-config                       # interactive y/N, panel scope
sudo 3m-ui reset-config --panel --yes        # scripted rescue (common case)
sudo 3m-ui reset-config --all --yes          # full reset
sudo 3m-ui reset-config --help               # full help (no service touched)
Smoke-tested with a fake binary: dispatch + flag passthrough + env vars
all correct; --help does not stop the service.
feat(scripts): wire reset-config into 3m-ui CLI wrapper + install hint
The new '3m-ui reset-config' Go subcommand (commit 8639b01) lets SSH
operators undo panel misconfigurations (wrong port / 127.0.0.1 bind /
broken SSL). This change exposes it through the systemd management
wrapper and documents it in the install banner.
scripts/3m-ui.sh:
- Add 'reset_config' function: stops the panel service (required by
the Go binary since it writes config.yaml + DB rows the running
panel might cache), invokes 3m-ui-bin reset-config <flags>, then
restarts the panel.
- --help / -h short-circuits the stop/restart cycle (read-only).
- Add 'reset-config' to the main case dispatch.
- Document the new subcommand + flags in usage() with examples.
scripts/install.sh:
- Append a line to the post-install banner pointing operators at
'3m-ui reset-config --panel --yes' for SSH rescue scenarios.
USAGE
sudo 3m-ui reset-config                       # interactive y/N, panel scope
sudo 3m-ui reset-config --panel --yes        # scripted rescue (common case)
sudo 3m-ui reset-config --all --yes          # full reset
sudo 3m-ui reset-config --help               # full help (no service touched)
Smoke-tested with a fake binary: dispatch + flag passthrough + env vars
all correct; --help does not stop the service.
feat(scripts): wire reset-config into 3m-ui CLI wrapper + install hint
The new '3m-ui reset-config' Go subcommand (commit 8639b01) lets SSH
operators undo panel misconfigurations (wrong port / 127.0.0.1 bind /
broken SSL). This change exposes it through the systemd management
wrapper and documents it in the install banner.
scripts/3m-ui.sh:
- Add 'reset_config' function: stops the panel service (required by
the Go binary since it writes config.yaml + DB rows the running
panel might cache), invokes 3m-ui-bin reset-config <flags>, then
restarts the panel.
- --help / -h short-circuits the stop/restart cycle (read-only).
- Add 'reset-config' to the main case dispatch.
- Document the new subcommand + flags in usage() with examples.
scripts/install.sh:
- Append a line to the post-install banner pointing operators at
'3m-ui reset-config --panel --yes' for SSH rescue scenarios.
USAGE
sudo 3m-ui reset-config                       # interactive y/N, panel scope
sudo 3m-ui reset-config --panel --yes        # scripted rescue (common case)
sudo 3m-ui reset-config --all --yes          # full reset
sudo 3m-ui reset-config --help               # full help (no service touched)
Smoke-tested with a fake binary: dispatch + flag passthrough + env vars
all correct; --help does not stop the service.
 2026-09-25 06:22:39 +00:00
freephilx 2e6256fb6a feat(distribution): add complete installation and recovery workflows 
Ship stable-only Linux bundles and multiarch Docker images with a pinned Mihomo core. Share secure first-run initialization across native and container installs.
Validate downloads before downtime, snapshot persistent state before updates, and restore the previous installation after a failed upgrade. Add backup, restore, healthcheck, and randomized administrator reset commands.
Add release verification, lifecycle regression tests, and installation documentation.
feat(distribution): add complete installation and recovery workflows
Ship stable-only Linux bundles and multiarch Docker images with a pinned Mihomo core. Share secure first-run initialization across native and container installs.
Validate downloads before downtime, snapshot persistent state before updates, and restore the previous installation after a failed upgrade. Add backup, restore, healthcheck, and randomized administrator reset commands.
Add release verification, lifecycle regression tests, and installation documentation.
feat(distribution): add complete installation and recovery workflows
Ship stable-only Linux bundles and multiarch Docker images with a pinned Mihomo core. Share secure first-run initialization across native and container installs.
Validate downloads before downtime, snapshot persistent state before updates, and restore the previous installation after a failed upgrade. Add backup, restore, healthcheck, and randomized administrator reset commands.
Add release verification, lifecycle regression tests, and installation documentation.
feat(distribution): add complete installation and recovery workflows
Ship stable-only Linux bundles and multiarch Docker images with a pinned Mihomo core. Share secure first-run initialization across native and container installs.
Validate downloads before downtime, snapshot persistent state before updates, and restore the previous installation after a failed upgrade. Add backup, restore, healthcheck, and randomized administrator reset commands.
Add release verification, lifecycle regression tests, and installation documentation.
feat(distribution): add complete installation and recovery workflows
Ship stable-only Linux bundles and multiarch Docker images with a pinned Mihomo core. Share secure first-run initialization across native and container installs.
Validate downloads before downtime, snapshot persistent state before updates, and restore the previous installation after a failed upgrade. Add backup, restore, healthcheck, and randomized administrator reset commands.
Add release verification, lifecycle regression tests, and installation documentation.
feat(distribution): add complete installation and recovery workflows
Ship stable-only Linux bundles and multiarch Docker images with a pinned Mihomo core. Share secure first-run initialization across native and container installs.
Validate downloads before downtime, snapshot persistent state before updates, and restore the previous installation after a failed upgrade. Add backup, restore, healthcheck, and randomized administrator reset commands.
Add release verification, lifecycle regression tests, and installation documentation.
feat(distribution): add complete installation and recovery workflows
Ship stable-only Linux bundles and multiarch Docker images with a pinned Mihomo core. Share secure first-run initialization across native and container installs.
Validate downloads before downtime, snapshot persistent state before updates, and restore the previous installation after a failed upgrade. Add backup, restore, healthcheck, and randomized administrator reset commands.
Add release verification, lifecycle regression tests, and installation documentation.
feat(distribution): add complete installation and recovery workflows
Ship stable-only Linux bundles and multiarch Docker images with a pinned Mihomo core. Share secure first-run initialization across native and container installs.
Validate downloads before downtime, snapshot persistent state before updates, and restore the previous installation after a failed upgrade. Add backup, restore, healthcheck, and randomized administrator reset commands.
Add release verification, lifecycle regression tests, and installation documentation.
feat(distribution): add complete installation and recovery workflows
Ship stable-only Linux bundles and multiarch Docker images with a pinned Mihomo core. Share secure first-run initialization across native and container installs.
Validate downloads before downtime, snapshot persistent state before updates, and restore the previous installation after a failed upgrade. Add backup, restore, healthcheck, and randomized administrator reset commands.
Add release verification, lifecycle regression tests, and installation documentation.
feat(distribution): add complete installation and recovery workflows
Ship stable-only Linux bundles and multiarch Docker images with a pinned Mihomo core. Share secure first-run initialization across native and container installs.
Validate downloads before downtime, snapshot persistent state before updates, and restore the previous installation after a failed upgrade. Add backup, restore, healthcheck, and randomized administrator reset commands.
Add release verification, lifecycle regression tests, and installation documentation.
feat(distribution): add complete installation and recovery workflows
Ship stable-only Linux bundles and multiarch Docker images with a pinned Mihomo core. Share secure first-run initialization across native and container installs.
Validate downloads before downtime, snapshot persistent state before updates, and restore the previous installation after a failed upgrade. Add backup, restore, healthcheck, and randomized administrator reset commands.
Add release verification, lifecycle regression tests, and installation documentation.
feat(distribution): add complete installation and recovery workflows
Ship stable-only Linux bundles and multiarch Docker images with a pinned Mihomo core. Share secure first-run initialization across native and container installs.
Validate downloads before downtime, snapshot persistent state before updates, and restore the previous installation after a failed upgrade. Add backup, restore, healthcheck, and randomized administrator reset commands.
Add release verification, lifecycle regression tests, and installation documentation.
 2026-09-08 22:47:35 +08:00
Z User 2fd6992574 feat(scripts): add config port command to 3m-ui management scripts 
Users changing the panel port from the web UI had to SSH in and run
'systemctl restart 3m-ui' manually — easy to forget and not discoverable.
Now both the 3m-ui entry script and 3m-ui.sh manager support:
3m-ui config show              — display config.yaml
3m-ui config port <1-65535>    — change port + auto-restart
The interactive menu (running '3m-ui' with no args) also gains:
9. 修改面板端口  (interactive port change with current/new display)
a. 卸载 3m-ui    (moved from slot 9 to 'a')
Flow:
1. Reads current port from config.yaml
2. Validates new port (1-65535, numeric)
3. sed replaces '  port: N' line in config.yaml
4. Restarts the service
5. Waits 1s, checks if active
6. Prints new access URL or failure message
This closes the UX gap: web UI saves port → user runs '3m-ui config
port 9000' → script restarts and confirms.
feat(scripts): add config port command to 3m-ui management scripts
Users changing the panel port from the web UI had to SSH in and run
'systemctl restart 3m-ui' manually — easy to forget and not discoverable.
Now both the 3m-ui entry script and 3m-ui.sh manager support:
3m-ui config show              — display config.yaml
3m-ui config port <1-65535>    — change port + auto-restart
The interactive menu (running '3m-ui' with no args) also gains:
9. 修改面板端口  (interactive port change with current/new display)
a. 卸载 3m-ui    (moved from slot 9 to 'a')
Flow:
1. Reads current port from config.yaml
2. Validates new port (1-65535, numeric)
3. sed replaces '  port: N' line in config.yaml
4. Restarts the service
5. Waits 1s, checks if active
6. Prints new access URL or failure message
This closes the UX gap: web UI saves port → user runs '3m-ui config
port 9000' → script restarts and confirms.
feat(scripts): add config port command to 3m-ui management scripts
Users changing the panel port from the web UI had to SSH in and run
'systemctl restart 3m-ui' manually — easy to forget and not discoverable.
Now both the 3m-ui entry script and 3m-ui.sh manager support:
3m-ui config show              — display config.yaml
3m-ui config port <1-65535>    — change port + auto-restart
The interactive menu (running '3m-ui' with no args) also gains:
9. 修改面板端口  (interactive port change with current/new display)
a. 卸载 3m-ui    (moved from slot 9 to 'a')
Flow:
1. Reads current port from config.yaml
2. Validates new port (1-65535, numeric)
3. sed replaces '  port: N' line in config.yaml
4. Restarts the service
5. Waits 1s, checks if active
6. Prints new access URL or failure message
This closes the UX gap: web UI saves port → user runs '3m-ui config
port 9000' → script restarts and confirms.
feat(scripts): add config port command to 3m-ui management scripts
Users changing the panel port from the web UI had to SSH in and run
'systemctl restart 3m-ui' manually — easy to forget and not discoverable.
Now both the 3m-ui entry script and 3m-ui.sh manager support:
3m-ui config show              — display config.yaml
3m-ui config port <1-65535>    — change port + auto-restart
The interactive menu (running '3m-ui' with no args) also gains:
9. 修改面板端口  (interactive port change with current/new display)
a. 卸载 3m-ui    (moved from slot 9 to 'a')
Flow:
1. Reads current port from config.yaml
2. Validates new port (1-65535, numeric)
3. sed replaces '  port: N' line in config.yaml
4. Restarts the service
5. Waits 1s, checks if active
6. Prints new access URL or failure message
This closes the UX gap: web UI saves port → user runs '3m-ui config
port 9000' → script restarts and confirms.
feat(scripts): add config port command to 3m-ui management scripts
Users changing the panel port from the web UI had to SSH in and run
'systemctl restart 3m-ui' manually — easy to forget and not discoverable.
Now both the 3m-ui entry script and 3m-ui.sh manager support:
3m-ui config show              — display config.yaml
3m-ui config port <1-65535>    — change port + auto-restart
The interactive menu (running '3m-ui' with no args) also gains:
9. 修改面板端口  (interactive port change with current/new display)
a. 卸载 3m-ui    (moved from slot 9 to 'a')
Flow:
1. Reads current port from config.yaml
2. Validates new port (1-65535, numeric)
3. sed replaces '  port: N' line in config.yaml
4. Restarts the service
5. Waits 1s, checks if active
6. Prints new access URL or failure message
This closes the UX gap: web UI saves port → user runs '3m-ui config
port 9000' → script restarts and confirms.
feat(scripts): add config port command to 3m-ui management scripts
Users changing the panel port from the web UI had to SSH in and run
'systemctl restart 3m-ui' manually — easy to forget and not discoverable.
Now both the 3m-ui entry script and 3m-ui.sh manager support:
3m-ui config show              — display config.yaml
3m-ui config port <1-65535>    — change port + auto-restart
The interactive menu (running '3m-ui' with no args) also gains:
9. 修改面板端口  (interactive port change with current/new display)
a. 卸载 3m-ui    (moved from slot 9 to 'a')
Flow:
1. Reads current port from config.yaml
2. Validates new port (1-65535, numeric)
3. sed replaces '  port: N' line in config.yaml
4. Restarts the service
5. Waits 1s, checks if active
6. Prints new access URL or failure message
This closes the UX gap: web UI saves port → user runs '3m-ui config
port 9000' → script restarts and confirms.
feat(scripts): add config port command to 3m-ui management scripts
Users changing the panel port from the web UI had to SSH in and run
'systemctl restart 3m-ui' manually — easy to forget and not discoverable.
Now both the 3m-ui entry script and 3m-ui.sh manager support:
3m-ui config show              — display config.yaml
3m-ui config port <1-65535>    — change port + auto-restart
The interactive menu (running '3m-ui' with no args) also gains:
9. 修改面板端口  (interactive port change with current/new display)
a. 卸载 3m-ui    (moved from slot 9 to 'a')
Flow:
1. Reads current port from config.yaml
2. Validates new port (1-65535, numeric)
3. sed replaces '  port: N' line in config.yaml
4. Restarts the service
5. Waits 1s, checks if active
6. Prints new access URL or failure message
This closes the UX gap: web UI saves port → user runs '3m-ui config
port 9000' → script restarts and confirms.
feat(scripts): add config port command to 3m-ui management scripts
Users changing the panel port from the web UI had to SSH in and run
'systemctl restart 3m-ui' manually — easy to forget and not discoverable.
Now both the 3m-ui entry script and 3m-ui.sh manager support:
3m-ui config show              — display config.yaml
3m-ui config port <1-65535>    — change port + auto-restart
The interactive menu (running '3m-ui' with no args) also gains:
9. 修改面板端口  (interactive port change with current/new display)
a. 卸载 3m-ui    (moved from slot 9 to 'a')
Flow:
1. Reads current port from config.yaml
2. Validates new port (1-65535, numeric)
3. sed replaces '  port: N' line in config.yaml
4. Restarts the service
5. Waits 1s, checks if active
6. Prints new access URL or failure message
This closes the UX gap: web UI saves port → user runs '3m-ui config
port 9000' → script restarts and confirms.
feat(scripts): add config port command to 3m-ui management scripts
Users changing the panel port from the web UI had to SSH in and run
'systemctl restart 3m-ui' manually — easy to forget and not discoverable.
Now both the 3m-ui entry script and 3m-ui.sh manager support:
3m-ui config show              — display config.yaml
3m-ui config port <1-65535>    — change port + auto-restart
The interactive menu (running '3m-ui' with no args) also gains:
9. 修改面板端口  (interactive port change with current/new display)
a. 卸载 3m-ui    (moved from slot 9 to 'a')
Flow:
1. Reads current port from config.yaml
2. Validates new port (1-65535, numeric)
3. sed replaces '  port: N' line in config.yaml
4. Restarts the service
5. Waits 1s, checks if active
6. Prints new access URL or failure message
This closes the UX gap: web UI saves port → user runs '3m-ui config
port 9000' → script restarts and confirms.
feat(scripts): add config port command to 3m-ui management scripts
Users changing the panel port from the web UI had to SSH in and run
'systemctl restart 3m-ui' manually — easy to forget and not discoverable.
Now both the 3m-ui entry script and 3m-ui.sh manager support:
3m-ui config show              — display config.yaml
3m-ui config port <1-65535>    — change port + auto-restart
The interactive menu (running '3m-ui' with no args) also gains:
9. 修改面板端口  (interactive port change with current/new display)
a. 卸载 3m-ui    (moved from slot 9 to 'a')
Flow:
1. Reads current port from config.yaml
2. Validates new port (1-65535, numeric)
3. sed replaces '  port: N' line in config.yaml
4. Restarts the service
5. Waits 1s, checks if active
6. Prints new access URL or failure message
This closes the UX gap: web UI saves port → user runs '3m-ui config
port 9000' → script restarts and confirms.
feat(scripts): add config port command to 3m-ui management scripts
Users changing the panel port from the web UI had to SSH in and run
'systemctl restart 3m-ui' manually — easy to forget and not discoverable.
Now both the 3m-ui entry script and 3m-ui.sh manager support:
3m-ui config show              — display config.yaml
3m-ui config port <1-65535>    — change port + auto-restart
The interactive menu (running '3m-ui' with no args) also gains:
9. 修改面板端口  (interactive port change with current/new display)
a. 卸载 3m-ui    (moved from slot 9 to 'a')
Flow:
1. Reads current port from config.yaml
2. Validates new port (1-65535, numeric)
3. sed replaces '  port: N' line in config.yaml
4. Restarts the service
5. Waits 1s, checks if active
6. Prints new access URL or failure message
This closes the UX gap: web UI saves port → user runs '3m-ui config
port 9000' → script restarts and confirms.
feat(scripts): add config port command to 3m-ui management scripts
Users changing the panel port from the web UI had to SSH in and run
'systemctl restart 3m-ui' manually — easy to forget and not discoverable.
Now both the 3m-ui entry script and 3m-ui.sh manager support:
3m-ui config show              — display config.yaml
3m-ui config port <1-65535>    — change port + auto-restart
The interactive menu (running '3m-ui' with no args) also gains:
9. 修改面板端口  (interactive port change with current/new display)
a. 卸载 3m-ui    (moved from slot 9 to 'a')
Flow:
1. Reads current port from config.yaml
2. Validates new port (1-65535, numeric)
3. sed replaces '  port: N' line in config.yaml
4. Restarts the service
5. Waits 1s, checks if active
6. Prints new access URL or failure message
This closes the UX gap: web UI saves port → user runs '3m-ui config
port 9000' → script restarts and confirms.
 2026-08-30 09:41:36 +00:00
dzx941 5b4cb63a73 fix: align listener generation with mihomo official spec 
- Port now supports mihomo ports format (single/range/list)
- Add explicit RoutingMark field support
- Auto-propagate UDP flag for vmess/vless/trojan/anytls/trusttunnel
- Update validator to accept port ranges
- Sync visual config and client converter port types
- Rename module from dzx941 to kazeyukiro
- Fix missing ExpiresAt in JWTClaims
- Fix nodeDTO Port type to string
- Fix frontend tsconfig and add missing dependencies
 2026-08-16 09:21:42 +08:00