docs: fix selfrun cargo-run instructions - #46
Merged
Conversation
sshaplygin
force-pushed
the
fix/selfrun-linux-docs
branch
from
August 9, 2026 13:03
027ed6f to
009c640
Compare
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.
Fixes #35.
The default cargo run launcher is not a cluster-compatible worker on either macOS or typical Linux. Document the portable flow: build the static musl worker, set YT_WORKER_BINARY, then run the host launcher.
Also distinguish that two-artifact flow from the optional direct-static self-upload path, including stale-artifact guidance and the example's e2e output.
Validation: