upstream/keycloak
1
0
Fork 0
mirror of https://github.com/keycloak/keycloak.git synced 2026-06-04 06:15:42 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 16

fix: removing doc that suggests using the config file for quarkus props (#35820)

Browse source 
closes: #35770

Signed-off-by: Steve Hawkins <shawkins@redhat.com>
This commit is contained in:
Steven Hawkins 2024-12-11 10:35:38 -05:00 committed by GitHub
parent a43b65281d
commit 27eaaefc4f
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 1 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/guides/server/configuration.adoc
View file

@ -142,9 +142,7 @@ You can use only a https://github.com/keycloak/keycloak/blob/main/quarkus/runtim
* A lock icon for a Quarkus property in the https://quarkus.io/guides/all-config[Quarkus documentation] indicates a build time property. You run the `build` command to apply this property. For details about the build command, see the subsequent sections on optimizing {project_name}.
* No lock icon for a property in the Quarkus guide indicates a runtime property for Quarkus and {project_name}.
. Use the `[-cf|--config-file]` command line parameter to include that file.
Similarly, you can also store Quarkus properties in a Java KeyStore.
You can also store Quarkus properties in a Java KeyStore.
Note that some Quarkus properties are already mapped in the {project_name} configuration, such as `quarkus.http.port` and similar essential properties. If the property is used by {project_Name}, defining that property key in `quarkus.properties` has no effect. The {project_Name} configuration value takes precedence over the Quarkus property value.