Repository navigation
Show sandbox nodes around Core and simplify node enrollment - #59
Merged
Merged
Conversation
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
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.
The Hosted Sandbox Manager now puts nodes around Core in a desktop topology, with connection-state animation, node selection and details, and secondary deployment metadata. Add node opens a compact verified installation command with clipboard feedback and enrollment progress. Chinese/English, keyboard access, reduced motion, existing authorization and resource guards are preserved; mobile redesign is deferred.
Initial setup uses a usable HTTPS console origin automatically and requires an explicit reachable address for loopback or unspecified origins. The installer reports its progress without printing credentials. No scheduling or provider lifecycle behavior changes.
Validation:
make checkwas run: backend/database/generated/distribution/SDK checks passed; it stops at those four pre-existing Dashboard failures. Remaining Mcode and Rust executor gates passed separately. This is not a fully greenmake checkresult.