-
Notifications
You must be signed in to change notification settings - Fork 0
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.
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
Keycloak upgrade #5
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
caddy_data |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1 @@ | ||
* @devnoname120 @roosnic1 @dominicdoerigswisstxt @RudolfSchreier | ||
* @devnoname120 @roosnic1 @RudolfSchreier @swisstxtsokol |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,6 @@ | ||
# keycloak-with-socket-factory | ||
|
||
# TODO: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Are there stories to do these TODOs? I am always a fan of putting a Jira story id on TODOs so it is clear if is more of a nice-to-have style TODO or an actual lets-do-this-next kind of TODO. |
||
- Add info how to build postgres-socket-factory https://github.com/GoogleCloudPlatform/cloud-sql-jdbc-socket-factory | ||
- Add info how to build jgroups-google | ||
- add info about preview features |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,38 @@ | ||
version: '3.8' | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The change itself was a bit contentious, but I would not go back through all of them to remove it, but if you are adding a new one, I think it would be better to leave it out. (Totally optional change though 😆) |
||
|
||
services: | ||
keycloak: | ||
build: | ||
context: . | ||
dockerfile: Dockerfile | ||
environment: | ||
KEYCLOAK_ADMIN: admin | ||
KEYCLOAK_ADMIN_PASSWORD: password | ||
Comment on lines
+9
to
+10
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is there a safety mechanism so that we don't accidentally use these weak credentials in production? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I agree with @swisstxtsokol (If I understood the comment right, please LMK!):
instead would force the developer to think about it at least once and avoid inadvertent mistakes. (As free bonus, it would also reduce duplication of the DB username/password) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Maybe move the |
||
KC_DB: postgres | ||
KC_DB_URL: jdbc:postgresql://db:5432/keycloak | ||
KC_DB_USERNAME: keycloak | ||
KC_DB_PASSWORD: keycloak | ||
Comment on lines
+13
to
+14
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. ditto: Is there a safety mechanism so that we don't accidentally use these weak credentials in production? |
||
KC_HOSTNAME: localhost | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should it be the url of our keycloak instance? |
||
JAVA_OPTS_APPEND: -Djgroups.dns.query=keycloak-headless | ||
command: | ||
- start | ||
- --hostname=localhost | ||
- --proxy=edge | ||
- --optimized | ||
ports: | ||
- "8080:8080" | ||
- "8443:8443" | ||
depends_on: | ||
- db | ||
|
||
db: | ||
image: postgres:latest | ||
environment: | ||
POSTGRES_DB: keycloak | ||
POSTGRES_USER: keycloak | ||
POSTGRES_PASSWORD: keycloak | ||
Comment on lines
+32
to
+33
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. ditto: Is there a safety mechanism so that we don't accidentally use these weak credentials in production? |
||
volumes: | ||
- postgres_data:/var/lib/postgresql/data | ||
|
||
volumes: | ||
postgres_data: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the difference between these two?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@devnoname120 the first one is the image with
phasetwo
plugin, the second one is pure keycloakThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok in this case I suggest to remove the commented out code: