No description
- FreeMarker 48.7%
- Java 34.9%
- CSS 11.8%
- JavaScript 2.4%
- Dockerfile 1.3%
- Other 0.9%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
Niko Köbler
3ee704918dAvoid re-trying BuildKit parallelism limits, build caching and per-platform builds, which were evaluated and dropped as ineffective or too complex. Signed-off-by: Niko Köbler <niko@n-k.de> |
||
| .forgejo/workflows | ||
| .github | ||
| .mvn/wrapper | ||
| .run | ||
| src | ||
| .editorconfig | ||
| .gitignore | ||
| build-with-docker.sh | ||
| CLAUDE.md | ||
| deploy.sh | ||
| docker-compose.yml | ||
| Dockerfile | ||
| mvnw | ||
| mvnw.cmd | ||
| pom.xml | ||
| README.md | ||
Keycloak Extensions
General
These custom extensions are based on
Current container image:
Building the Binaries
You can build the binaries, if you have a local installation of JDK, with
$ ./mvnw clean package
If you don't have local JDK installation, but Docker is available, you can use the helper script
$ ./build-with-docker.sh
Both approaches will build the binary target/keycloak-extensions.jar.
Deployment
Deploy the built JAR file into the $KEYCLOAK_HOME/providers folder of your Keycloak server (or copy it to your Docker image).
When running Keycloak in optimized mode, you'll have to run a build after deploying the JAR.
If you start Keycloak regularly, an implicit build will be performed.
See Keycloak Docs and Keycloak Guides for more info.
Extensions
t.b.d.