Document sprite exec port auto-forwarding#181
Open
kcmartin wants to merge 1 commit into
Open
Conversation
Contributor
Preview Deployment
Commit: |
Contributor
Lighthouse Results
|
Contributor
E2E Test Results✅ Tests success Ran against: https://pr-181-superfly-sprites-docs.fly.dev |
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
Documents the auto-forwarding behavior of
sprite execand updates the Port Conflicts section to reference the new--no-port-forwardflag and the improvedsprite proxyerror message. Both ship in superfly/sprite-env#468 (merged, awaiting the next rc; available on the dev channel today).Changes
sprite execcalling out that listening ports get auto-forwarded locally, with a pointer to--no-port-forward.The auto-generated
cli/commands.mdxwill pick up the new flag on the next CLI doc regeneration; no manual edit needed there.Relates to #154. I'll close that issue once the rc with the binary fix ships.