Repository navigation
Conversation
This branch has not been deployed
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.
What does this PR do?
Adds Pethost as a row of the one-click deployment table in
README.md, after Railyard, in the same shape.It links to https://pethost.dev/templates/authorizer/, a one-click template that runs
quay.io/authorizer/authorizerwith SQLite, its URL, client id and secrets set per deployment and the admin secret the user chooses. I deployed it, signed in to the dashboard with the admin secret and was refused with a wrong one, checked that the OpenID configuration gives the https issuer, and restarted it with its data kept.Which issue(s) does this PR fix?
None.
If this PR affects any API reference documentation, please share the updated endpoint references
It does not.