Skip to content

Conversation

@dutow
Copy link
Collaborator

@dutow dutow commented Nov 13, 2025

This is just a simple setup that users can try out without setting up anything manually, if they have docker installed.

127.0.0.1 keycloak
```

This allows your browser to resolve the `https://keycloak:8443` URLs used in the OAuth device flow.
Copy link
Collaborator

Choose a reason for hiding this comment

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

URLs -> URL


# Wait for services to be ready
# Optional: watch the logs while waiting
docker compose logs -f
Copy link
Collaborator

Choose a reason for hiding this comment

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

I personally prefer to just run it without -d, then I can see the logs without having to run -f also and can kill everything with ^C. But maybe it is better this way so you do not need to explain you need two shells.

- ../../test/import:/opt/keycloak/data/import
- ./certs:/keys
ports:
- "8443:8443"
Copy link
Collaborator

Choose a reason for hiding this comment

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

We want to be explicit about it only listening to 127.0.0.1 since I believe 0.0.0.0 is the default listen but correct me if I am wrong. And we do not want to expose an open admin UI to everyone on the same LAN.

volumes:
- ./certs/crt.pem:/usr/local/share/ca-certificates/keycloak-test.crt:ro
ports:
- "5432:5432"
Copy link
Collaborator

Choose a reason for hiding this comment

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

You probably want to pick another port at the host since many run PG on 5432.

This is just a simple setup that users can try out without setting up
anything manually, if they have docker installed.
@dutow dutow requested a review from jeltz November 18, 2025 15:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants