Add a tutorial to deploy Keycloak in cluster mode#3622
Conversation
EtienneM
left a comment
EtienneM
left a comment
There was a problem hiding this comment.
praise: that's great, I don't have much to say about this :)
src/_tutorials/keycloak/index.md
Outdated
| This tutorial covers the deployment of Keycloak on Scalingo. Configuring, | ||
| managing, and administrating Keycloak is out of the scope of this tutorial. |
There was a problem hiding this comment.
suggestion: add a link to the Keycloak documentations for these?
src/_tutorials/keycloak/index.md
Outdated
| 5. (optional) Create credentials for the initial administrator user: | ||
| ```bash | ||
| scalingo --app my-keycloak env-set KC_BOOTSTRAP_ADMIN_USERNAME=<admin_username> | ||
| scalingo --app my-keycloak env-set KC_BOOTSTRAP_ADMIN_PASSWORD=<admin_password> | ||
| ``` |
There was a problem hiding this comment.
question: what is the admin password if we don't set this? If it's insecure to not set an admin password, I would mark this step as mandatory
There was a problem hiding this comment.
You're right, I've made them mandatory (well they technically aren't but they are if you follow the doc) in c57358e
If the user don't create them, Keycloak will ask them to create one... but the interface is only available on localhost. So it won't work.
src/_tutorials/keycloak/index.md
Outdated
|
|
||
| - Review the official changelog that is published with each release. Breaking | ||
| and notable changes should catch your attention. | ||
| - Ensure your SPIs and themes are compatible with the new version. |
There was a problem hiding this comment.
I've added a link to the little explanation we have in ffd9547
| Moreover, the buildpack makes use of the following environment variables. They | ||
| can be leveraged to customize your deployment: | ||
|
|
||
| - `KEYCLOAK_VERSION`\\ |
There was a problem hiding this comment.
question: that makes me think: do we have a NewReleases configuration to track Keycloak releases?
There was a problem hiding this comment.
I don't think so.
Actually, updating the default version in the buildpack is something I'd like to automate through GitHub Action.
In the meantime, and until it's done, you're right, let's add it :)
Co-authored-by: Étienne M. <EtienneM@users.noreply.github.com>
SPIs are ~explained in the Customizing section.
3 participants
No description provided.