docs: clarify Scope live-runner setup#2
Draft
fastagents wants to merge 2 commits into
Draft
Conversation
fastagents
force-pushed
the
codex/scope-live-runner-setup
branch
from
b90b9b4 to
241d765
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.
Summary
This clarifies the Scope live-runner startup command and documents an optional model-preload workflow for operators who want warm model caches before serving traffic.
Code/docs changes
docker-compose.yml, run the Scope runner asuv run --extra livepeer livepeer-scope.README.md, add a model-preload command usinguv run --extra livepeer python ..., with the registry import beforedownload_models().Why
The current upstream compose file still starts the runner with
uv run livepeer-scope. Using thelivepeeroptional extra keeps the runner startup path aligned with the live-runner dependency set.