Repository navigation
Fix isolated self-hosted uploader build paths - #24
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
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 isolated self-hosted smoke test copies its Compose file into a temporary directory. The rebuilt uploader and trust mounts still pointed outside that directory, causing startup to fail with
lstat /deploy.Copy the uploader build context and trust bundle into the isolated installation, override their relative paths, and build the local uploader in the installer instead of trying to pull a nonexistent remote tag. The regular installation now uses the uploader-only build context.
Validation: source and isolated Compose layouts resolve all build contexts and bind sources; shell syntax checks and all seven release-tool tests pass. A fresh local image built from this exact head passed the full self-hosted journey: owner bootstrap/login, API authentication/create/read/update, signed resumable upload, real media processing, public player/manifest, full HLS decode, private upload storage and analytics ingestion/readback. Remote CI must also finish green before merge; release publication retains the same complete smoke gate.