mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 21:46:22 +01:00
fix toc issue
This commit is contained in:
@@ -3,6 +3,7 @@
|
||||
include::modules/developer-cli-odo-attributes.adoc[]
|
||||
include::modules/common-attributes.adoc[]
|
||||
:context: configuring-the-odo-cli
|
||||
|
||||
toc::[]
|
||||
|
||||
include::modules/developer-cli-odo-using-command-completion.adoc[leveloffset=+1]
|
||||
|
||||
@@ -3,6 +3,7 @@
|
||||
include::modules/developer-cli-odo-attributes.adoc[]
|
||||
include::modules/common-attributes.adoc[]
|
||||
:context: creating-instances-of-services-managed-by-operators
|
||||
|
||||
toc::[]
|
||||
|
||||
Operators are a method of packaging, deploying, and managing Kubernetes services. With `{odo-title}`, you can create instances of services from the custom resource definitions (CRDs) provided by the Operators. You can then use these instances in your projects and link them to your components.
|
||||
|
||||
@@ -3,6 +3,7 @@
|
||||
include::modules/developer-cli-odo-attributes.adoc[]
|
||||
include::modules/common-attributes.adoc[]
|
||||
:context: creating-a-java-application-with-a-database
|
||||
|
||||
toc::[]
|
||||
|
||||
This example describes how to deploy a Java application by using devfile and connect it to a database service.
|
||||
|
||||
@@ -3,6 +3,7 @@
|
||||
include::modules/developer-cli-odo-attributes.adoc[]
|
||||
include::modules/common-attributes.adoc[]
|
||||
:context: creating-a-multicomponent-application-with-odo
|
||||
|
||||
toc::[]
|
||||
|
||||
`{odo-title}` allows you to create a multicomponent application, modify it, and link its components in an easy and automated way.
|
||||
|
||||
@@ -3,6 +3,7 @@
|
||||
include::modules/developer-cli-odo-attributes.adoc[]
|
||||
include::modules/common-attributes.adoc[]
|
||||
:context: creating-a-single-component-application-with-odo
|
||||
|
||||
toc::[]
|
||||
|
||||
With `{odo-title}`, you can create and deploy applications on clusters.
|
||||
|
||||
@@ -3,6 +3,7 @@
|
||||
include::modules/developer-cli-odo-attributes.adoc[]
|
||||
include::modules/common-attributes.adoc[]
|
||||
:context: creating-an-application-with-a-database
|
||||
|
||||
toc::[]
|
||||
|
||||
This example describes how to deploy and connect a database to a front-end application.
|
||||
|
||||
@@ -3,6 +3,7 @@
|
||||
include::modules/developer-cli-odo-attributes.adoc[]
|
||||
include::modules/common-attributes.adoc[]
|
||||
:context: debugging-applications-in-odo
|
||||
|
||||
toc::[]
|
||||
|
||||
With `{odo-title}`, you can attach a debugger to remotely debug your application. This feature is only supported for NodeJS and Java components.
|
||||
|
||||
@@ -3,6 +3,7 @@
|
||||
include::modules/developer-cli-odo-attributes.adoc[]
|
||||
include::modules/common-attributes.adoc[]
|
||||
:context: deleting-applications
|
||||
|
||||
toc::[]
|
||||
|
||||
You can delete applications and all components associated with the application in your project.
|
||||
|
||||
@@ -3,6 +3,7 @@
|
||||
include::modules/developer-cli-odo-attributes.adoc[]
|
||||
include::modules/common-attributes.adoc[]
|
||||
:context: using-sample-applications
|
||||
|
||||
toc::[]
|
||||
|
||||
`{odo-title}` offers partial compatibility with any language or runtime listed within the OpenShift catalog of component types. For example:
|
||||
|
||||
@@ -3,6 +3,7 @@
|
||||
include::modules/developer-cli-odo-attributes.adoc[]
|
||||
include::modules/common-attributes.adoc[]
|
||||
:context: creating-applications-by-using-devfiles
|
||||
|
||||
toc::[]
|
||||
|
||||
include::modules/developer-cli-odo-about-devfiles-in-odo.adoc[leveloffset=+1]
|
||||
|
||||
@@ -3,6 +3,7 @@
|
||||
include::modules/developer-cli-odo-attributes.adoc[]
|
||||
include::modules/common-attributes.adoc[]
|
||||
:context: working-with-projects
|
||||
|
||||
toc::[]
|
||||
|
||||
Project keeps your source code, tests, and libraries organized in a separate single unit.
|
||||
|
||||
@@ -3,6 +3,7 @@
|
||||
include::modules/developer-cli-odo-attributes.adoc[]
|
||||
include::modules/common-attributes.adoc[]
|
||||
:context: working-with-storage
|
||||
|
||||
toc::[]
|
||||
|
||||
Persistent storage keeps data available between restarts of `{odo-title}`.
|
||||
|
||||
@@ -3,6 +3,7 @@
|
||||
include::modules/developer-cli-odo-attributes.adoc[]
|
||||
include::modules/common-attributes.adoc[]
|
||||
:context: installing-odo
|
||||
|
||||
toc::[]
|
||||
|
||||
The following section describes how to install `{odo-title}` on different platforms using the CLI or the Visual Studio Code (VS Code) IDE.
|
||||
|
||||
@@ -3,6 +3,7 @@
|
||||
include::modules/developer-cli-odo-attributes.adoc[]
|
||||
include::modules/common-attributes.adoc[]
|
||||
:context: managing-environment-variables
|
||||
|
||||
toc::[]
|
||||
|
||||
`{odo-title}` stores component-specific configurations and environment variables in the `config` file. You can use the `odo config` command to set, unset, and list environment variables for components without the need to modify the `config` file.
|
||||
|
||||
@@ -3,6 +3,7 @@
|
||||
include::modules/developer-cli-odo-attributes.adoc[]
|
||||
include::modules/common-attributes.adoc[]
|
||||
:context: odo-architecture
|
||||
|
||||
toc::[]
|
||||
|
||||
This section describes `{odo-title}` architecture and how `{odo-title}` manages resources on a cluster.
|
||||
|
||||
@@ -3,6 +3,7 @@
|
||||
include::modules/developer-cli-odo-attributes.adoc[]
|
||||
include::modules/common-attributes.adoc[]
|
||||
:context: odo-cli-reference
|
||||
|
||||
toc::[]
|
||||
|
||||
include::modules/developer-cli-odo-basic-odo-cli-commands.adoc[leveloffset=+1]
|
||||
|
||||
@@ -3,6 +3,7 @@
|
||||
include::modules/developer-cli-odo-attributes.adoc[]
|
||||
include::modules/common-attributes.adoc[]
|
||||
:context: odo-release-notes
|
||||
|
||||
toc::[]
|
||||
|
||||
[id="odo-notable-improvements_{context}"]
|
||||
|
||||
@@ -3,6 +3,7 @@
|
||||
include::modules/developer-cli-odo-attributes.adoc[]
|
||||
include::modules/common-attributes.adoc[]
|
||||
:context: understanding-odo
|
||||
|
||||
toc::[]
|
||||
|
||||
`{odo-title}` is a CLI tool for creating applications on {product-title} and Kubernetes. With `{odo-title}`, you can write, build, and debug applications on a cluster without the need to administer the cluster itself.
|
||||
|
||||
@@ -3,6 +3,7 @@
|
||||
include::modules/developer-cli-odo-attributes.adoc[]
|
||||
include::modules/common-attributes.adoc[]
|
||||
:context: about-odo-in-a-restricted-environment
|
||||
|
||||
toc::[]
|
||||
|
||||
|
||||
|
||||
@@ -3,6 +3,7 @@
|
||||
include::modules/developer-cli-odo-attributes.adoc[]
|
||||
include::modules/common-attributes.adoc[]
|
||||
:context: creating-and-deploying-a-component-to-the-disconnected-cluster
|
||||
|
||||
toc::[]
|
||||
|
||||
After you push the `init` image to a cluster with a mirrored registry, you must mirror a supported builder image for your application with the `oc` tool, overwrite the mirror registry using the environment variable, and then create your component.
|
||||
|
||||
@@ -3,6 +3,7 @@
|
||||
include::modules/developer-cli-odo-attributes.adoc[]
|
||||
include::modules/common-attributes.adoc[]
|
||||
:context: pushing-the-odo-init-image-to-the-restricted-cluster-registry
|
||||
|
||||
toc::[]
|
||||
|
||||
Depending on the configuration of your cluster and your operating system you can either push the `odo` init image to a mirror registry or directly to an internal registry.
|
||||
|
||||
Reference in New Issue
Block a user