Simplify the docs referencing the container registry (#23874)

Closes #23873
This commit is contained in:
Alexander Schwartz 2023-10-11 08:53:28 +02:00 committed by GitHub
parent 8871983b33
commit e672ea4f8e
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 2 deletions

View file

@ -216,7 +216,7 @@ Keycloak only allows to create the initial admin user from a local network conne
== Importing A Realm On Startup
The https://quay.io/keycloak/keycloak[published Keycloak containers] have a directory `/opt/keycloak/data/import`. If you put one or more import files in that directory via a volume mount or other means and add the startup argument `--import-realm`, the Keycloak container will import that data on startup! This may only make sense to do in Dev mode.
The Keycloak containers have a directory `/opt/keycloak/data/import`. If you put one or more import files in that directory via a volume mount or other means and add the startup argument `--import-realm`, the Keycloak container will import that data on startup! This may only make sense to do in Dev mode.
[source, bash]
----

View file

@ -102,7 +102,7 @@ You are also able to import realms when the server is starting by using the `--i
When you set the `--import-realm` option, the server is going to try to import any realm configuration file from the `data/import` directory. Only regular files using the `.json` extension are read from this directory, sub-directories are ignored.
NOTE: For the https://quay.io/keycloak/keycloak[published containers], the import directory is `/opt/keycloak/data/import`
NOTE: For the Keycloak containers, the import directory is `/opt/keycloak/data/import`
If a realm already exists in the server, the import operation is skipped. The main reason behind this behavior is to avoid re-creating
realms and potentially loose state between server restarts.