Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Make Keycloak persistent #244

Merged
merged 3 commits into from
Dec 21, 2023
Merged

Make Keycloak persistent #244

merged 3 commits into from
Dec 21, 2023

Conversation

josvandervelde
Copy link

The Keycloak container should save the state to the filesystem. That way, it can safely go down.

This PR makes sure Keycloak:

  1. runs in production mode
  2. saves to filesystem (default production behavior)
  3. only imports the realm if the realm doesn't exist (default behavior)

We might want to improve this lateron by using a different database, but this should be fine for now.

I tested it by:

  • docker compose up -d
  • log in to Keycloak as admin, add a user
  • docker compose down
  • docker compose up -d
  • check if user still exists

@jsmatias jsmatias self-requested a review December 21, 2023 14:17
jsmatias
jsmatias approved these changes Dec 21, 2023
View reviewed changes
Copy link
Member

@jsmatias jsmatias left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All good. I also tested as explained in your description and it works as expected. ✌️

@josvandervelde josvandervelde merged commit 968f502 into develop Dec 21, 2023
1 check passed
@josvandervelde josvandervelde deleted the bugfix/persistent-keycloak branch December 21, 2023 18:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jsmatias jsmatias jsmatias approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@josvandervelde @jsmatias