feat(settings): Developer Options with LAN devnet import#181
Merged
Conversation
Add a Developer Options section to Settings > Advanced for testing against non-production networks: - LAN devnet: paste a host:port for an `ant-devnet --serve-port` host; the app fetches its manifest (import_devnet_manifest_url), writes it to the shared data dir, and restarts to run against it exactly like a local devnet. Disconnect clears the manifest and reverts to production. The host/port is persisted (AppConfig) and the manifest is re-fetched fresh each launch, since a devnet restart changes ports and the wallet key. - Move the pre-release builds toggle into this section. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Nic-dorman
force-pushed
the
feat/lan-devnet-manifest
branch
from
979cbf7 to
4927418
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a Developer Options section to Settings → Advanced for testing against non-production networks. Consumes the manifest served by ant-node#174 (
ant-devnet --serve-port). (Sibling PR for upload/download changes is separate.)LAN devnet
host:portfor anant-devnet --serve-porthost. Apply & Restart fetches its manifest (import_devnet_manifest_url→GET /api/devnet-manifest.json), validates it, and writes it to the shared data dir — the same file a local devnet uses — then restarts, so the existingload_devnet_manifeststartup path connects to it exactly like a local devnet. The client already auto-detects LAN vs loopback from the bootstrap IPs, so no connection-layer change was needed.clear_devnet_manifest) and reverts to production.host:portis persisted (AppConfig.lan_devnet_host/port) so it's remembered, but the manifest is re-fetched fresh each launch — a devnet restart changes ports and the wallet key, so a cached manifest would be silently stale.host:portbox (tolerates anhttp://prefix / trailing path).Also
Notes
http://LAN hosts work.Builds clean (
tauri dev); manifest import + restart flow exercised against a local devnet.🤖 Generated with Claude Code