Migration: Master Dev Guide

Author: vikram-redhat

architecture/core_concepts/routes.adoc

@@ -365,6 +365,7 @@ A secured route is one that specifies the TLS termination of the route.
 The available types of termination are xref:secured-routes[described
 below].
 
+[[path-based-routes]]
 == Path Based Routes
 Path based routes specify a path component that can be compared against
 a URL (which requires that the traffic for the route be HTTP based) such

dev_guide/app_tutorials/quickstarts.adoc

@@ -14,15 +14,15 @@ toc::[]
 
 A quickstart is a basic example of an application running on {product-title}.
 Quickstarts come in a variety of languages and frameworks, and are defined in a
-link:../../dev_guide/templates.html[template], which is constructed from a set
+xref:../../dev_guide/templates.adoc#dev-guide-templates[template], which is constructed from a set
 of services, build configurations, and deployment configurations. This template
 references the necessary images and source repositories to build and deploy the
 application.
 
 To explore a quickstart, create an application from a template. Your
 administrator may have already installed these templates in your {product-title}
 cluster, in which case you can simply select it from the web console. See the
-link:../../dev_guide/templates.html[template] documentation for more information
+xref:../../dev_guide/templates.adoc#dev-guide-templates[template] documentation for more information
 on how to upload, create from, and modify a template.
 
 Quickstarts refer to a source repository that contains the application source

dev_guide/app_tutorials/ruby_on_rails.adoc

@@ -37,12 +37,12 @@ First make sure that an instance of {product-title} is running and is available.
 ifdef::openshift-enterprise,openshift-origin[]
 For
 more info on how to get {product-title} up and running check the
-link:../../install_config/install/index.html[installation methods].
+xref:../../install_config/install/index.adoc#install-config-install-index[installation methods].
 endif::[]
-Also make sure that your link:../../cli_reference/get_started_cli.html[`oc` CLI
+Also make sure that your xref:../../cli_reference/get_started_cli.adoc#cli-reference-get-started-cli[`oc` CLI
 client is installed] and the command is accessible from your command shell, so
 you can use it to
-link:../../cli_reference/get_started_cli.html#basic-setup-and-login[log in]
+xref:../../cli_reference/get_started_cli.adoc#basic-setup-and-login[log in]
 using your email address and password.
 
 === Setting Up the Database
@@ -167,7 +167,7 @@ If you don't see the page, check the logs that are output to your server to debu
 
 === Configuring the Application for {product-title}
 
-In order to have your application communicating with the PostgreSQL database service that will be running in {product-title}, you will need to edit the `default` section in your `config/database.yml` to use link:../../using_images/db_images/postgresql.html#environment-variables[environment variables], which you will define later, upon the database service creation.
+In order to have your application communicating with the PostgreSQL database service that will be running in {product-title}, you will need to edit the `default` section in your `config/database.yml` to use xref:../../using_images/db_images/postgresql.adoc#postgresql-environment-variables[environment variables], which you will define later, upon the database service creation.
 
 The `default` section in your edited `config/database.yml` together with pre-defined variables should look like:
 
@@ -180,7 +180,7 @@ default: &default
   adapter: postgresql
   encoding: unicode
   # For details on connection pooling, see rails configuration guide
-  # http://guides.rubyonrails.org/configuring.html#database-pooling
+  # http://guides.rubyonrails.org/configuring.adoc#database-pooling
   pool: <%= ENV["POSTGRESQL_MAX_CONNECTIONS"] || 5 %>
   username: <%= user %>
   password: <%= password %>
@@ -242,26 +242,26 @@ $ git push
 
 == Deploying Your Application to {product-title}
 
-To deploy your Ruby on Rails application, create a new link:../projects.html[Project] for the application:
+To deploy your Ruby on Rails application, create a new xref:../projects.adoc#dev-guide-projects[Project] for the application:
 
 ----
 $ oc new-project rails-app --description="My Rails application" --display-name="Rails Application"
 ----
 
-After creating the the `rails-app` link:../projects.html[project], you will be automatically switched to the new project namespace.
+After creating the the `rails-app` xref:../projects.adoc#dev-guide-projects[project], you will be automatically switched to the new project namespace.
 
 Deploying your application in {product-title} involves three steps:
 
-* Creating a database link:../../architecture/core_concepts/pods_and_services.html#services[service] from {product-title}'s link:../../using_images/db_images/postgresql.html[PostgreSQL image]
-* Creating a frontend link:../../architecture/core_concepts/pods_and_services.html#services[service] from {product-title}'s link:../../using_images/s2i_images/ruby.html[Ruby 2.0 builder image] and your Ruby on Rails source code, which we wire with the database service
+* Creating a database xref:../../architecture/core_concepts/pods_and_services.adoc#services[service] from {product-title}'s xref:../../using_images/db_images/postgresql.adoc#using-images-db-images-postgresql[PostgreSQL image]
+* Creating a frontend xref:../../architecture/core_concepts/pods_and_services.adoc#services[service] from {product-title}'s xref:../../using_images/s2i_images/ruby.adoc#using-images-s2i-images-ruby[Ruby 2.0 builder image] and your Ruby on Rails source code, which we wire with the database service
 * Creating a route for your application.
 
 [[creating-the-database-service]]
 === Creating the Database Service
 
-Your Rails application expects a running database link:../../architecture/core_concepts/pods_and_services.html#services[service]. For this service use link:http://www.postgresql.org/[PostgeSQL] database link:../../using_images/db_images/postgresql.html[image].
+Your Rails application expects a running database xref:../../architecture/core_concepts/pods_and_services.adoc#services[service]. For this service use link:http://www.postgresql.org/[PostgeSQL] database xref:../../using_images/db_images/postgresql.adoc#using-images-db-images-postgresql[image].
 
-To create the database link:../../architecture/core_concepts/pods_and_services.html#services[service] you will use the link:../new_app.html[oc new-app] command. To this command you will need to pass some necessary link:../../using_images/db_images/postgresql.html#environment-variables[environment variables] which will be used inside the database container. These link:../../using_images/db_images/postgresql.html#environment-variables[environment variables] are required to set the username, password, and name of the database. You can change the values of these link:../../using_images/db_images/postgresql.html#environment-variables[environment variables] to anything you would like. The variables we are going to be setting are as follows:
+To create the database xref:../../architecture/core_concepts/pods_and_services.adoc#services[service] you will use the xref:../new_app.adoc#dev-guide-new-app[oc new-app] command. To this command you will need to pass some necessary xref:../../using_images/db_images/postgresql.adoc#environment-variables[environment variables] which will be used inside the database container. These xref:../../using_images/db_images/postgresql.adoc#environment-variables[environment variables] are required to set the username, password, and name of the database. You can change the values of these xref:../../using_images/db_images/postgresql.adoc#environment-variables[environment variables] to anything you would like. The variables we are going to be setting are as follows:
 
 * POSTGRESQL_DATABASE
 * POSTGRESQL_USER
@@ -293,15 +293,15 @@ $ oc get pods --watch
 
 === Creating the Frontend Service
 
-To bring your application to {product-title}, you need to specify a repository in which your application lives, using once again the link:../new_app.html[oc new-app] command, in which you will need to specify database related link:../../using_images/db_images/postgresql.html#environment-variables[environment variables] we setup in the link:./ruby_on_rails.html#creating-the-database-service[Creating the Database Service]:
+To bring your application to {product-title}, you need to specify a repository in which your application lives, using once again the xref:../new_app.adoc#dev-guide-new-app[oc new-app] command, in which you will need to specify database related xref:../../using_images/db_images/postgresql.adoc#environment-variables[environment variables] we setup in the xref:./ruby_on_rails.adoc#creating-the-database-service[Creating the Database Service]:
 
 ----
 $ oc new-app path/to/source/code --name=rails-app -e POSTGRESQL_USER=username -e POSTGRESQL_PASSWORD=password -e POSTGRESQL_DATABASE=db_name
 ----
 
-With this command, {product-title} fetches the source code, sets up the Builder image, link:../builds.html[builds] your application image, and deploys the newly created image together with the specified link:../../using_images/db_images/postgresql.html#environment-variables[environment variables]. The application is named `rails-app`.
+With this command, {product-title} fetches the source code, sets up the Builder image, xref:../builds.adoc#dev-guide-builds[builds] your application image, and deploys the newly created image together with the specified xref:../../using_images/db_images/postgresql.adoc#environment-variables[environment variables]. The application is named `rails-app`.
 
-You can verify the environment variables have been added by viewing the JSON document of the `rails-app` link:../deployments.html[DeploymentConfig]:
+You can verify the environment variables have been added by viewing the JSON document of the `rails-app` xref:../deployments.adoc#dev-guide-deployments[DeploymentConfig]:
 
 ----
 $ oc get dc rails-app -o json
@@ -326,13 +326,13 @@ env": [
 ],
 ----
 
-To check the link:../builds.html[build] process, use the link:../builds.html#accessing-build-logs[build-logs] command:
+To check the xref:../builds.adoc#dev-guide-builds[build] process, use the xref:../builds.adoc#accessing-build-logs[build-logs] command:
 
 ----
 $ oc logs -f build rails-app-1
 ----
 
-Once the link:../builds.html[build] is complete, you can look at the running link:../../architecture/core_concepts/pods_and_services.html#pods[pods] in {product-title}
+Once the xref:../builds.adoc#dev-guide-builds[build] is complete, you can look at the running xref:../../architecture/core_concepts/pods_and_services.adoc#pods[pods] in {product-title}
 
 ----
 $ oc get pods
@@ -344,7 +344,7 @@ Before your application will be functional, you need to initialize the database
 
 * Manually from the running frontend container:
 
-First you need to exec into frontend container with link:../../cli_reference/basic_cli_operations.html#troubleshooting-and-debugging-cli-operations[rsh] command:
+First you need to exec into frontend container with xref:../../cli_reference/basic_cli_operations.adoc#troubleshooting-and-debugging-cli-operations[rsh] command:
 
   $ oc rsh <FRONTEND_POD_ID>
 
@@ -354,11 +354,11 @@ Run the migration from inside the container:
 
 If you are running your Rails application in a `development` or `test` environment you don't have to specify the `RAILS_ENV` environment variable.
 
-* By adding pre-deployment link:../../dev_guide/deployments.html#lifecycle-hooks[lifecycle hooks] in your template. For example check the link:https://github.com/openshift/rails-ex/blob/master/openshift/templates/rails-postgresql.json#L122-L130[hooks example] in our link:https://github.com/openshift/rails-ex[Rails example] application.
+* By adding pre-deployment xref:../../dev_guide/deployments.adoc#lifecycle-hooks[lifecycle hooks] in your template. For example check the link:https://github.com/openshift/rails-ex/blob/master/openshift/templates/rails-postgresql.json#L122-L130[hooks example] in our link:https://github.com/openshift/rails-ex[Rails example] application.
 
 === Creating a Route for Your Application
 
-To expose a service by giving it an externally-reachable hostname like `www.example.com` use {product-title} link:../routes.html[route]. In your case you need to expose the frontend service by typing:
+To expose a service by giving it an externally-reachable hostname like `www.example.com` use {product-title} xref:../routes.adoc#dev-guide-routes[route]. In your case you need to expose the frontend service by typing:
 
 ----
 $ oc expose service rails-app --hostname=www.example.com
@@ -368,11 +368,11 @@ $ oc expose service rails-app --hostname=www.example.com
 ====
 It's the user's responsibility to ensure the hostname they specify resolves into the IP address of the router. For more information, check the {product-title} documentation on:
 ====
-* link:../../architecture/core_concepts/routes.html#routers[Routes]
+* xref:../../architecture/core_concepts/routes.adoc#routers[Routes]
 ifdef::openshift-enterprise,openshift-origin[]
-* link:../../admin_guide/high_availability.html#configuring-a-highly-available-routing-service[Configuring a Highly-available Routing Service]
+* xref:../../admin_guide/high_availability.adoc#configuring-a-highly-available-routing-service[Configuring a Highly-available Routing Service]
 endif::[]
 ifdef::openshift-dedicated[]
-* https://docs.openshift.com/enterprise/latest/admin_guide/high_availability.html#configuring-a-highly-available-routing-service[Configuring
+* https://docs.openshift.com/enterprise/latest/admin_guide/high_availability.adoc#configuring-a-highly-available-routing-service[Configuring
 a Highly-available Routing Service] (OpenShift Enterprise documentation)
 endif::[]

dev_guide/application_lifecycle.adoc

@@ -39,12 +39,12 @@ administrator within your organization.
 Develop::
 * Using your editor/IDE of choice, create a basic skeleton of an application. It
 should be developed enough to tell {product-title}
-link:../dev_guide/new_app.html#language-detection[what kind of application it
+xref:../dev_guide/new_app.adoc#language-detection[what kind of application it
 is].
 * Push the code to your Git repository.
 
 Generate::
-* link:../dev_guide/new_app.html[Create a basic application] using the `new-app`
+* xref:../dev_guide/new_app.adoc#dev-guide-new-app[Create a basic application] using the `new-app`
 command. {product-title} generates build and deployment configurations.
 
 Manage::
@@ -53,7 +53,7 @@ Manage::
 * Continue to locally develop and polish your code.
 * Push your code to a Git repository.
 * Is any extra configuration needed? Explore the
-link:../dev_guide/index.html[Developer Guide] for more options.
+xref:../dev_guide/index.adoc#dev-guide-index[Developer Guide] for more options.
 
 Verify::
 * You can verify your application in a number of ways. You can push your changes
@@ -85,7 +85,7 @@ Access to {product-title}::
 administrator within your organization.
 
 Generate::
-* link:../dev_guide/new_app.html[Create a basic application] using the `new-app`
+* xref:../dev_guide/new_app.adoc#dev-guide-new-app[Create a basic application] using the `new-app`
 command. {product-title} generates build and deployment configurations.
 
 Verify::
@@ -96,4 +96,4 @@ Manage::
 * Continue to develop your application code until you are happy with the results.
 * Rebuild your application in {product-title} to accept any newly pushed code.
 * Is any extra configuration needed? Explore the
-link:../dev_guide/index.html[Developer Guide] for more options.
+xref:../dev_guide/index.adoc#dev-guide-index[Developer Guide] for more options.

dev_guide/authentication.adoc

@@ -14,7 +14,7 @@ toc::[]
 
 == Web Console Authentication
 When accessing the
-link:../architecture/infrastructure_components/web_console.html[web console]
+xref:../architecture/infrastructure_components/web_console.adoc#architecture-infrastructure-components-web-console[web console]
 ifdef::openshift-origin,openshift-online,openshift-dedicated,openshift-origin[]
 from a browser at *<master_public_addr>:8443*, you are automatically redirected
 endif::[]
@@ -29,18 +29,18 @@ image::login_page.png["Web Console Login Page"]
 endif::[]
 
 Review the
-link:../architecture/infrastructure_components/web_console.html[browser versions
+xref:../architecture/infrastructure_components/web_console.adoc#architecture-infrastructure-components-web-console[browser versions
 and operating systems] that can be used to access the web console.
 
 You can provide your login credentials on this page to obtain a token to make
 API calls. After logging in, you can navigate your projects using the
-link:../architecture/infrastructure_components/web_console.html[web console].
+xref:../architecture/infrastructure_components/web_console.adoc#architecture-infrastructure-components-web-console[web console].
 
 [[cli-authentication]]
 
 == CLI Authentication
 You can authenticate from the command line using the CLI command `oc login`.
-You can link:../cli_reference/get_started_cli.html[get started with the CLI] by
+You can xref:../cli_reference/get_started_cli.adoc#cli-reference-get-started-cli[get started with the CLI] by
 running this command without any options:
 
 ----
@@ -51,7 +51,7 @@ The command's interactive flow helps you establish a session to an {product-titl
 server with the provided credentials. If any information required to successfully
 log in to an {product-title} server is not provided, the command prompts for user
 input as required. The
-link:../cli_reference/get_started_cli.html#cli-configuration-files[configuration]
+xref:../cli_reference/get_started_cli.adoc#cli-configuration-files[configuration]
 is automatically saved and is then used for every subsequent command.
 
 All configuration options for the `oc login` command, listed in the `oc login
@@ -123,17 +123,17 @@ for user input to confirm (`y/N` kind of input) about connecting insecurely.
 |===
 
 CLI configuration files allow you to easily
-link:../cli_reference/manage_cli_profiles.html[manage multiple CLI profiles].
+xref:../cli_reference/manage_cli_profiles.adoc#cli-reference-manage-cli-profiles[manage multiple CLI profiles].
 
 // tag::systemadminlogin[]
 
 [NOTE]
 ====
 If you have access to administrator credentials but are no longer logged in as
-the link:../architecture/core_concepts/projects_and_users.html#users[default
+the xref:../architecture/core_concepts/projects_and_users.adoc#users[default
 system user] *system:admin*, you can log back in as this user at any time as
 long as the credentials are still present in your
-link:../cli_reference/get_started_cli.html#cli-configuration-files[CLI
+xref:../cli_reference/get_started_cli.adoc#cli-configuration-files[CLI
 configuration file]. The following command logs in and switches to the *default*
 project: