From f94bf82cb6083182cd05d53fa8fdf57ad6fbfeef Mon Sep 17 00:00:00 2001 From: Jan Lieskovsky Date: Fri, 14 Dec 2018 19:36:15 +0100 Subject: [PATCH] [General] Drop the duplicate occurrence of the 'Deployment Process' paragraph Keep it in the 'Advanced Concepts' section, since that's the one, where it belongs (see 7.2 guide for reference) Signed-off-by: Jan Lieskovsky --- openshift/topics/advanced_concepts.adoc | 2 +- openshift/topics/get_started.adoc | 11 ----------- 2 files changed, 1 insertion(+), 12 deletions(-) diff --git a/openshift/topics/advanced_concepts.adoc b/openshift/topics/advanced_concepts.adoc index 93bedbb29e..44f1d13087 100644 --- a/openshift/topics/advanced_concepts.adoc +++ b/openshift/topics/advanced_concepts.adoc @@ -436,7 +436,7 @@ When restarting the server it is important to restart just the JBoss EAP process Once deployed, the *_{project_templates_version}-https_* and *_{project_templates_version}-x509-https_* templates create a single pod that contains both the database and the {project_name} servers. The *_{project_templates_version}-mysql_*, *_{project_templates_version}-mysql-persistent_*, *_{project_templates_version}-x509-mysql-persistent_*, *_{project_templates_version}-postgresql_*, *_{project_templates_version}-postgresql-persistent_*, and *_{project_templates_version}-x509-postgresql-persistent_* templates create two pods, one for the database server and one for the {project_name} web server. -After the {project_name} web server pod has started, it can be accessed from its custom configured hostnames, or from the default hostnames: +After the {project_name} web server pod has started, it can be accessed at its custom configured hostnames, or at the default hostnames: * *\http://sso-__.__/auth/admin*: for the {project_name} web server, and * *\https://secure-sso-__.__/auth/admin*: for the encrypted {project_name} web server. diff --git a/openshift/topics/get_started.adoc b/openshift/topics/get_started.adoc index 2660900d56..37fcb4f538 100644 --- a/openshift/topics/get_started.adoc +++ b/openshift/topics/get_started.adoc @@ -289,17 +289,6 @@ The {project_openshift_product_name} templates use TLS passthrough termination f For more information on OpenShift route types, see the link:https://docs.openshift.com/container-platform/3.7/architecture/networking/routes.html#route-types[Networking chapter] of the OpenShift Architecture Guide. -==== Deployment Process - -Once deployed, the *_{project_templates_version}-https_* and *_{project_templates_version}-x509-https_* templates create a single pod that contains both the database and the {project_name} servers. The *_{project_templates_version}-mysql_*, *_{project_templates_version}-mysql-persistent_*, *_{project_templates_version}-x509-mysql-persistent_*, *_{project_templates_version}-postgresql_*, *_{project_templates_version}-postgresql-persistent_*, and *_{project_templates_version}-x509-postgresql-persistent_* templates create two pods, one for the database server and one for the {project_name} web server. - -After the {project_name} web server pod has started, it can be accessed at its custom configured hostnames, or at the default hostnames: - -* *\http://sso-__.__/auth/admin*: for the {project_name} web server, and -* *\https://secure-sso-__.__/auth/admin*: for the encrypted {project_name} web server. - -Use the xref:../get_started/get_started.adoc#sso-administrator-setup[administrator user credentials] to log in into the `master` realm’s administration console. - [[SSO-Clients]] ==== {project_name} Clients