v0.1.0-rc.5 — NAS GUI installation and browser DHCP handover

rc.5 adds a manual NAS Docker-GUI installation path: import one Compose project, finish a browser wizard, then import the generated production Compose. No AI connection, SSH, host Python, JSON editing or local image build is required for this path. This is an experimental prerelease, not a universal NAS compatibility claim.

Downloads

• setup.compose.yaml: import into the NAS Docker project interface and change the one absolute folder path.
• Prebuilt x86-64 controller image: import through the NAS local-images interface if registry access is unavailable. This is a Docker image archive, not the source archive. Mihomo still requires its own image download.
• Source archive, manifest and SHA256SUMS are separate assets.

Follow the English GUI installation guide or 中文安装指南.

Changes

• Temporary Chinese/English browser setup protected by a per-start access code. Discover wired, bonded and bridge interfaces, IPv4 subnet and gateway; suggest fixed addresses and check responding ARP conflicts. Sleeping devices and reservations still need operator checks.
• Generate private runtime and an absolute-mount production Compose containing both services. Existing state is refused rather than overwritten; writes are staged and competing installers serialized. DHCP stays off during installation.
• Add authenticated, CSRF-protected DHCP joining/stop controls in panel Settings, with client-test, main-router-DHCP-off and sole-server confirmations. All five panel languages include recovery guidance.
• Support private runtime owned by a normal NAS account using scoped DAC_OVERRIDE inside containers, without mounting Docker socket or host root. Retain the optional manual and Docker terminal installers.
• Publish a versioned Linux/amd64 image and Docker-save archive. Runtime, setup, production image and source manifest version are 0.1.0-rc.5. Fix the previous Compose image-label mismatch without moving any older tag.

Validation and upgrade

102 source tests pass locally. Full main CI includes Compose parsing, image build, ordinary and foreign-UID offline startup/health/login, and isolated DHCP migration. Tag CI repeats these checks before image publication. Browser setup was tested with fictional data; actual NAS checks covered read-only bond0 detection and an occupied gateway address. Fresh installation on another real LAN remains unverified.

Existing deployments must not rerun setup. Privately back up state; GUI deployments update the controller image reference while retaining network addresses and runtime mounts. Existing device policies remain in runtime. DHCP is enabled only after testing a client and disabling other DHCP servers.

Requires an x86-64 Linux NAS with Docker Compose project support, host/macvlan networking and TUN, on the same LAN as clients. Installer supports IPv4 only; public IPv6 can bypass it. Automatic failover and forgotten-password recovery are not implemented. The initial routing/DNS preset targets mainland China.

Previous releases and their assets are preserved.

Main CI: https://github.com/AzBuildDev/nas-device-flow/actions/runs/37807599890
Tag tests and image publication: https://github.com/AzBuildDev/nas-device-flow/actions/runs/37807854623

Source commit: 070290f83f22417673df219942a2b2c1fb006031.

Registry verification: the GHCR package is Public. Anonymous access fetched the manifest, config and all seven layers (48,719,807 bytes) and verified SHA256 without supplying account credentials. Linux/amd64 image tag and OCI version label were verified; runtime source files in the Docker-save archive match the tag.

Manifest digest: sha256:532909e54a00e547f4c02d017abd00776c0ae5321f786d62165e27a8bef5e687.

SHA256SUMS covers the source archive, prebuilt image archive, setup Compose and manifest. The manifest records source-file hashes and registry metadata.