Custom error paths #12
Merged
Conversation
This file contains 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
kevinmcconnell
force-pushed
the
custom-error-path
branch
from
5537213 to
fff70e2
Compare
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.
Allows setting the path to a set of custom error templates, on a per-service basis. This is to allow people to brand the error pages to suit their apps. It's entirely optional -- if not set, we use the built-in templates.
To specify a path for error templates, use
--error-pageswhen deploying, e.g.:When a proxy error occurs, we'll first try to render a service-specific template, if they have been configured. If we don't have a template there (because there's no custom path, or because the path doesn't include a template for the error we're rendering) then we fall back to the default set.