libre.sh/keycloak-scim
2
0
Fork 0
Code Issues 14 Pull requests Releases Packages Activity Actions 6

fix: correcting the container examples wrt hostname (#33542)

Browse source 
closes: #33539

Signed-off-by: Steve Hawkins <shawkins@redhat.com>
This commit is contained in:
Steven Hawkins 2024-10-04 04:27:52 -04:00 committed by GitHub
parent 07a5782cc8
commit c092867c48
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
docs/guides/server/containers.adoc
View file

@ -136,7 +136,7 @@ To start the image, run:
podman|docker run --name mykeycloak -p 8443:8443 -p 9000:9000 \ podman|docker run --name mykeycloak -p 8443:8443 -p 9000:9000 \
-e KC_BOOTSTRAP_ADMIN_USERNAME=admin -e KC_BOOTSTRAP_ADMIN_PASSWORD=change_me \ -e KC_BOOTSTRAP_ADMIN_USERNAME=admin -e KC_BOOTSTRAP_ADMIN_PASSWORD=change_me \
mykeycloak \ mykeycloak \
start --optimized start --optimized --hostname=localhost
---- ----
{project_name} starts in production mode, using only secured HTTPS communication, and is available on `https://localhost:8443`. {project_name} starts in production mode, using only secured HTTPS communication, and is available on `https://localhost:8443`.
@ -149,7 +149,7 @@ Opening up `https://localhost:9000/metrics` leads to a page containing operation
By default, the server is listening for `http` and `https` requests using the ports `8080` and `8443`, respectively. By default, the server is listening for `http` and `https` requests using the ports `8080` and `8443`, respectively.
If you want to expose the container using a different port, you need to set the `hostname-port` accordingly: If you want to expose the container using a different port, you need to set the `hostname` accordingly:
. Exposing the container using a port other than the default ports . Exposing the container using a port other than the default ports
[source, bash] [source, bash]
@ -157,10 +157,10 @@ If you want to expose the container using a different port, you need to set the
podman|docker run --name mykeycloak -p 3000:8443 \ podman|docker run --name mykeycloak -p 3000:8443 \
-e KC_BOOTSTRAP_ADMIN_USERNAME=admin -e KC_BOOTSTRAP_ADMIN_PASSWORD=change_me \ -e KC_BOOTSTRAP_ADMIN_USERNAME=admin -e KC_BOOTSTRAP_ADMIN_PASSWORD=change_me \
mykeycloak \ mykeycloak \
start --optimized --hostname-port=3000 start --optimized --hostname=https://localhost:3000
---- ----
By setting the `hostname-port` option you can now access the server at `https://localhost:3000`. By setting the `hostname` option to a full url you can now access the server at `https://localhost:3000`.
== Trying {project_name} in development mode == Trying {project_name} in development mode
The easiest way to try {project_name} from a container for development or testing purposes is to use the Development mode. The easiest way to try {project_name} from a container for development or testing purposes is to use the Development mode.

2
docs/guides/server/reverseproxy.adoc
View file

@ -6,7 +6,7 @@
<@tmpl.guide <@tmpl.guide
title="Using a reverse proxy" title="Using a reverse proxy"
summary="Learn how to configure {project_name} together with a reverse proxy, api gateway, or load balancer." summary="Learn how to configure {project_name} together with a reverse proxy, api gateway, or load balancer."
includedOptions="proxy proxy-* hostname-path hostname-url http-relative-path"> includedOptions="proxy-* hostname hostname-admin http-relative-path">
Distributed environments frequently require the use of a reverse proxy. {project_name} offers several options to securely integrate with such environments. Distributed environments frequently require the use of a reverse proxy. {project_name} offers several options to securely integrate with such environments.