fix(compose): support a TorBox-only setup#5
Merged
Conversation
compose.yml hard-required RD_API_TOKEN (${RD_API_TOKEN:?...}) and never passed TORBOX_API_KEY to the container, so a TorBox-only .env failed at compose interpolation before the container started — contradicting the app's exactly-one-provider design.
Pass both tokens with an empty default (${VAR:-}) instead; choose_provider already trims and drops empty tokens, so the unset one is treated as absent and the app selects whichever is non-empty (erroring clearly if neither or both are set).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
compose.ymlhard-requiredRD_API_TOKEN(${RD_API_TOKEN:?…}) and never passedTORBOX_API_KEYto the container, so a TorBox-only.envfailed at compose interpolation — before the container even started — contradicting the app's exactly-one-provider design.Now both tokens are passed with an empty default (
${VAR:-});choose_provideralready trims and drops empty tokens, so the unset one is treated as absent and the app selects whichever is non-empty (and errors clearly if neither or both are set).Validated with
docker compose config(interpolation resolves cleanly). Config-only change — no Rust code touched.