Merged
Conversation
bfops
added
the
docs deploy whenever
Centril
pushed a commit
that referenced
this pull request
Mar 3, 2026
# Description of Changes Closes #4496. The docs refer to a block mentioning `/v1/publish` but we don't have such a block in our example config. What we actually have is: ``` # Block all other routes explicitly. Only localhost can use these routes. If you want to open your # server up so that anyone can publish to it you should comment this section out. location / { allow 127.0.0.1; deny all; } ``` # API and ABI breaking changes None. # Expected complexity level and risk 1. # Testing None Co-authored-by: Zeke Foppa <bfops@users.noreply.github.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
2 participants
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.
Description of Changes
Closes #4496.
The docs refer to a block mentioning
/v1/publishbut we don't have such a block in our example config. What we actually have is:API and ABI breaking changes
None.
Expected complexity level and risk
Testing
None