Set up independent Dev platform with automatic verified updates - #6
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
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.
The Dev platform now runs independently from its own owner login and DSPs, using
dev/livefor code and siblingconfig,data, anddspsdirectories for private state. Accounts use separate first and last names throughout bootstrap, invitations, and account settings.Successful GitHub push checks on
devupload a verified runtime artifact. A Dev-only systemd updater checks the merged commit and artifact digests, updates the checkout and compiled build together, verifies health, and restores the previous build after a failed start. It preserves private state and refuses unfinished checkout changes or automatic schema transitions. Includes first-setup tooling, Cloudflare Tunnel service, browser host verification, and operating documentation.Validation covers service/security tests, independent Dev state, name migration, updater success/failure/recovery, compiled supervisor tests, browser UI flows, native browser isolation, and strict Chromium namespace/seccomp sandbox acceptance on the Dev host. CI runs the repository checks and publishes artifacts only for successful
devpush builds.Production provisioning and release publishing/deployment automation remain deferred. The existing legacy gateway tests are retained for compatibility; standalone Dev disables that activation flow.