Proposal: Mount providers directory as a Docker volume #25
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I propose to mount the Keycloak
/opt/keycloak/providersdirectory in the Docker container to a localprovidersfolder inside the project, using a Docker volume. This makes it possible to test themes for production by creating a.jarfile (i.e..zipfile renamed to.jar) of the contents of thesrcfolder and moving it into the newprovidersfolder.Q: But why add it by default? Can't the developers add the volume when they need it?
A: Docker volumes cannot be added to a container after the container has been created. So if the developers realize they need the
providersfolder, they need to re-create the container, and possibly lose their configuration.I also added a
.gitkeepfile to theprovidersfolder as well, so that it is immediately apparent where to put the custom providers when cloning the repo.LMK if you want me to add documentation for this folder to
README.mdas well.