Feat/multi proxy support#3
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.
This pull request introduces support for running multiple YARP proxy + devtunnel pairs from a single AppHost, replacing the previous single-proxy setup. Each proxy/tunnel pair is now configured via its own JSON file in a new
src/AppHost/proxies/directory, enabling independent configuration of routes, CORS, and access mode per pair. The README and code are updated to reflect the new workflow, and a detailed design document is added. The changes also improve testability and error handling for configuration issues.Multiple proxy/tunnel pair support:
src/AppHost/AppHost.cs: Rewritten to scan theproxies/folder for JSON files, creating a proxy/tunnel pair for each valid file. The filename determines the slug and resource names, and per-pair access mode is loaded from the file. Startup fails with clear errors for invalid filenames or an empty folder.README.md: Updated throughout to explain the new multi-proxy workflow, including quickstart, migration, and advanced scenarios. Instructions and examples now reference the per-pair JSON files insrc/AppHost/proxies/. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]Design and documentation:
docs/superpowers/specs/2026-05-07-multiple-proxies-design.md: Added a comprehensive design document detailing goals, topology, config schema, migration, and testing for the new multi-proxy support.Other improvements:
src/AppHost/AppHost.csproj: Updated Aspire.Hosting.DevTunnels package to version 13.3.0.These changes make it easy to add, remove, and independently configure multiple proxy/tunnel pairs, improving flexibility and maintainability for local development workflows.