Find a file
2024-06-22 03:36:24 +02:00
.devcontainer Migrate to Keycloakify v10 2024-06-06 05:26:06 +02:00
.github/workflows Support prerelease 2024-06-22 03:36:24 +02:00
.storybook Remove storybook addons 2024-06-09 15:13:39 +02:00
public Don't use SspCloud as terms placeholder 2024-06-06 06:39:16 +02:00
src Remove useDownloadTerms from starter 2024-06-21 20:56:39 +02:00
.eslintrc.cjs Migrate to Keycloakify v10 2024-06-06 05:26:06 +02:00
.gitignore Working build 2024-02-12 02:00:54 +01:00
.prettierignore Migrate to Keycloakify v10 2024-06-06 05:26:06 +02:00
.prettierrc.json update 2024-06-07 05:20:57 +02:00
index.html Migrate to Keycloakify v10 2024-06-06 05:26:06 +02:00
LICENSE Initial commit 2022-09-06 19:22:23 +02:00
package.json Reset back to 0.0.0 2024-06-22 03:29:08 +02:00
README.md Update how terms 2024-06-21 02:31:13 +02:00
tsconfig.json Migrate to Keycloakify v10 2024-06-06 05:26:06 +02:00
tsconfig.node.json Migrate to Keycloakify v10 2024-06-06 05:26:06 +02:00
vite.config.ts Use vanilla vite config 2024-06-16 02:36:06 +02:00
yarn.lock Update keycloakify 2024-06-22 03:05:39 +02:00

🚀 Keycloakify v10 starter 🚀

This starter is based on Vite. There is also a Webpack based starter.

Quick start

git clone https://github.com/keycloakify/keycloakify-starter
cd keycloakify-starter
yarn install # Or use an other package manager, just be sure to delete the yarn.lock if you do.

Testing the theme locally

Documentation

How to customize the theme

Documentation

Building the theme

You need to have Maven installed to build the theme (The mvn command must be in the PATH).

  • On macOS: brew install maven
  • On Debian/Ubuntu: sudo apt-get install maven
  • On Windows: choco install openjdk and choco install maven (Or download from here)
npm run build-keycloak-theme

Note that by default Keycloakify generates multiple .jar files for different versions of Keycloak.
You can customize this behavior, see documentation here.

GitHub Actions

The starter comes with a generic GitHub Actions workflow that builds the theme and publishes the jars as GitHub releases artifacts.
To release a new version just update the package.json version and push.

To enable the workflow go to your fork of this repository on GitHub then navigate to: Settings > Actions > Workflow permissions, select Read and write permissions.