Make Compose startup self-contained - #412
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.
A downloaded release
compose.yamlnow publishes Web on127.0.0.1:8080by default and initializes entirely from its image. Users no longer need a second Compose file or a first-start download of the full release control archive.oacand four node metadata files in a scratch initialization image; pin its registry digest and validate release identity and metadata checksums.compose.yaml, retainOAC_HOST/OAC_WEB_PORT, removeports.yamland the installer’sCOMPOSE_FILEsetting, and update release assets and development callers.portsblock. Dokploy metadata now selectsweb.Validation: Go init/Web tests; 22 distribution manifest, 38 publisher, 4 Compose, 36 CI selection and 5 Linux amd64 installer tests; translation, name, shell syntax and diff checks. Compose smoke verifies startup, sign-in, API, uploads, node installer and persistent restart with init networking disabled. Scratch initialization and database-image cleanup were also tested directly. The scratch test image is 2,375,530 bytes uncompressed, including approximately 128 KB of metadata; it contains no control archive or execution artifacts.
Full Linux platform coverage runs in CI. Independent review covers the complete change.