Repository navigation
Ship local and remote setup with project-centered deployment management - #115
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.
Visitors can now start GroundControl from their computer, choose local Docker or an existing Linux server, and open the private setup link printed by the launcher. Projects now represent an application with folder or GitHub sources and separate deployment instances; users can connect an existing workload or launch a new one, and dismiss discovery suggestions.
The change includes desktop-aware onboarding, a folder picker, grouped discovery, additive project migrations, and updated installation and release documentation. Existing runtime records and workload locations are preserved.
Publishing is separated from updating the operator VPS: a main merge builds a candidate image, clean server and desktop acceptance must pass before
latestis promoted, and the production VPS deployment requires an explicit manual workflow input. This merge does not request a production restart.Validation: 501 application tests and production build passed after merging latest main; all 9 launcher tests passed; desktop host execution regression passed; populated-database migration check preserved all 48 existing tables, relationships and values. CI and anonymous clean-install acceptance provide the remaining release checks.