Allow Pluribus to publish pages via its own ingress tenant - #50
Merged
Merged
Conversation
assistant-ngalaiko
Bot
force-pushed
the
pluribus/publishing-ingress
branch
from
September 20, 2026 12:17
20b9bfd to
4e7591e
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.
Adds a dedicated /pluribus/* public ingress tenant on port 8084 with a user-owned Caddyfile and reload socket. No access to root routing or other tenants. No Hello World seed; uses the standard unconfigured-route 404 until pages are published at runtime. Requires merge and deployment; live ingress unchanged.