feat(proxy): support managed dynamic extensions - #129
Merged
Conversation
Generate managed static configuration when proxy.config contains only dynamic files, while preserving full custom static ownership when a Traefik config is present.\n\nCreate the nested dynamic mountpoint before Docker binds it beneath the read-only configuration mount.
vishr
force-pushed
the
fix/proxy-dynamic-mountpoint
branch
from
August 28, 2026 02:26
bbac7f2 to
8972444
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
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
Why
Adding one middleware should not require applications to duplicate entrypoints, discovery, health, and ACME configuration. Static install policy stays managed by default; dynamic routing policy remains extensible, with full static configuration as the escape hatch.
Verification