fix paths

openshift-instruqt · Jul 11, 2024 · 15b4a90 · 15b4a90
1 parent dd0c418
commit 15b4a90
Show file tree

Hide file tree

Showing 7 changed files with 32 additions and 31 deletions.
diff --git a/...ng-the-cluster-deploying-python/01-01-creating-an-initial-project/assignment.md b/...ng-the-cluster-deploying-python/01-01-creating-an-initial-project/assignment.md
@@ -104,27 +104,27 @@ You can now log into the OpenShift web console using the `admin/admin` username/
 
 You'll be presented with a login page as shown in the figure below.
 
-![Login](..\assets\web-console-login.png)
+![Login](../assets/web-console-login.png)
 
 |NOTE:|
 |----|
 |You might see the following warning notification due to using an untrusted security certificate.
-![Security warning](..\assets\security_warning.png)
+![Security warning](../assets/security_warning.png)
 If you do get the warning, click the **Advanced** button to complete the process necessary to grant permission to the browser to access the OpenShift Web Console.|
 
 Use the `admin/admin` username/password pair to login.
 
 Once logged in, you will be in the **Administrator** perspective. Notice that the first item in the vertical menu bar of the OpenShift console has the label **Administrator** as shown in the figure below:
 
-![Admin Perspective](..\assets\admin-perspective.png)
+![Admin Perspective](../assets/admin-perspective.png)
 
 Next you'll change to the **Developer** perspective.
 
 # Changing to the Developer perspective
 
 `Step 4 :`  Select `Developer` from the drop-down as shown in the figure below to change to the **Developer** perspective.
 
-![Change to Developer](..\assets\change-to-developer.png)
+![Change to Developer](../assets/change-to-developer.png)
 
 Next, you'll select the project you created previously in the OpenShift web console.
 
@@ -139,11 +139,11 @@ Next, you'll select the project you created previously in the OpenShift web cons
 
 The details of these 3 previous actions are shown in the figure below.
 
-![Select MyProject](..\assets\select-my-project.png)
+![Select MyProject](../assets/select-my-project.png)
 
 You'll be presented with an **Add** page that has a collection of text blocks as shown in the figure below.
 
-![MyProject Result](..\assets\my-project-result.png)
+![MyProject Result](../assets/my-project-result.png)
 
 # Congratulations!
 

diff --git a/...ing-the-cluster-deploying-python/02-join-red-hat-developer-portal/assignment.md b/...ing-the-cluster-deploying-python/02-join-red-hat-developer-portal/assignment.md
@@ -1,6 +1,6 @@
 ---
 slug: join-red-hat-developer-portal
-id: t1upyjvcdv43
+id: fs97sddupuuh
 type: challenge
 title: Join Red Hat Developer at no cost
 teaser: Join Red Hat Developer at no cost

diff --git a/...he-cluster-deploying-python/03-02-deploying-using-the-web-console/assignment.md b/...he-cluster-deploying-python/03-02-deploying-using-the-web-console/assignment.md
@@ -28,7 +28,7 @@ First, we need to select the type of application you're deploying. The first thi
 
 `Step 1b:` Scroll down a bit and click the **All services** text in the **Developer Catalog** text block as shown in the figure below.
 
-![All Services](..\assets\all-services.png)
+![All Services](../assets/all-services.png)
 
 ----
 
@@ -40,15 +40,15 @@ This action filters out all text blocks except those that are relevant to Python
 
 `Step 2b:` Select the text block labeled **Python** as shown in the figure below.
 
-![Select Python](..\assets\select-python.png)
+![Select Python](../assets/select-python.png)
 
 You'll be presented with a web page that is particular to the Python service you've just selected.
 
 ----
 
 `Step 3:` Click the Create button as shown in the figure below.
 
-![Create app](..\assets\app-create.png)
+![Create app](../assets/app-create.png)
 
 You'll be presented with a web page titled **Create to Source-To-Image application**.
 
@@ -66,26 +66,26 @@ https://github.com/openshift-instruqt/blog-django-py
 
 Into the **Git Repo URL** text box, as shown in the figure below.
 
-![Bind Source Code](..\assets\app-git.png)
+![Bind Source Code](../assets/app-git.png)
 
 ----
 
 `Step 5a:` Scroll down the page. Notice that the **Create to Source-To-Image Application** web page has automatically filled in values in the **Application** and **Name** text boxes in the **General** section as shown in the figure below:
 
-![General](..\assets\app-general.png)
+![General](../assets/app-general.png)
 
 Keep scrolling.
 
 Notice in the **Advanced options** section, as shown in the figure below, that **Create a route to the Application** checkbox is selected. This means that OpenShift will automatically create a URL that allows access to the application from the Internet.
 
-![Advanced](..\assets\app-advanced.png)
+![Advanced](../assets/app-advanced.png)
 
 
 `Step 5b:` Finally, click the **Create** button, as shown in the figure above. This action will save the source code data and start the build process for the application.
 
 You will be presented with the Topology overview page in the OpenShift web console while the build is in progress, as shown in the figure below.
 
-![Topology page](..\assets\topology.png)
+![Topology page](../assets/topology.png)
 
 # Anatomy of an application graphic in the Topology overview
 
@@ -95,7 +95,7 @@ Notice that the graphic for the Python application shown above has a blue circle
 
 The color of the circle and the icons surrounding the circle have special meanings. The figure below describes the meaning of each of these graphical elements.
 
-![Anatomy of an App](..\assets\anatomy-of-app.png)
+![Anatomy of an App](../assets/anatomy-of-app.png)
 
 The Git icon shown to the lower right of the ring can be clicked on to take you to the hosted Git repository from which the source code for the application was built.
 
@@ -107,11 +107,11 @@ The ring itself will progress from white, indicating the deployment is pending,
 
 Clicking anywhere on the area enclosed by the ring will bring up a panel giving details of the resources for the application as shown in the figure below.
 
-![Deployment details](..\assets\graphic-n-data.png)
+![Deployment details](../assets/graphic-n-data.png)
 
 # Congratulations!
 
 You've started the process of deploying a Python application using the OpenShift web console and the Create to Source-To-Image Application feature.
 
 ----
-**NEXT:** Viewing the build logs for a deployment in the OpenShift Web Console
+**NEXT:** Viewing the build logs for a deployment in the OpenShift Web Console
diff --git a/...using-the-cluster-deploying-python/04-03-viewing-the-builder-logs/assignment.md b/...using-the-cluster-deploying-python/04-03-viewing-the-builder-logs/assignment.md
@@ -26,7 +26,7 @@ In this topic, you will learn how to view a deployment's logs from within the Op
 
 Make sure you are in the Topology overview page in the OpenShift web console. You'll see the graphic for the Python application deployment.
 
-![App Topology](..\assets\app-topology-python.png)
+![App Topology](../assets/app-topology-python.png)
 
 ----
 
@@ -38,11 +38,11 @@ You'll see a button on the lower right with the label, **View logs**.
 
 `Step 3:` Click the **View logs** button as shown in the figure below.
 
-![View Logs 1](..\assets\view-logs-01.png)
+![View Logs 1](../assets/view-logs-01.png)
 
 When you click the **View logs** button, you'll be presented with a panel that displays a continuous stream of log data, as shown in the figure below.
 
-![View Logs 2](..\assets\view-logs-02.png)
+![View Logs 2](../assets/view-logs-02.png)
 
 Viewing the deployment logs allows you to monitor the progress of the build as it runs. When the build completes successfully, you see a final message, "Push successful". This indicates that the container image for the application was pushed to the OpenShift internal image registry, and the application is up and running.
 
@@ -52,4 +52,4 @@ You've just learned how to view a deployment's logs in the OpenShift web console
 
 ----
 
-**NEXT:** Access the application from the Internet
+**NEXT:** Access the application from the Internet
diff --git a/...sing-the-cluster-deploying-python/05-04-accessing-the-application/assignment.md b/...sing-the-cluster-deploying-python/05-04-accessing-the-application/assignment.md
@@ -25,23 +25,23 @@ In the previous topics, you built and deployed the Python application. In this t
 
 Click on **Topology** button in the left-hand menu bar to return to the topology view for the project.
 
-![Topology View](..\assets\topology.png)
+![Topology View](../assets/topology.png)
 
 As you read in a previous topic, when you created the application using the web console, an OpenShift `route` was automatically created for the application. The `route` exposed the application outside of the cluster to the Internet. You'll use the `route`'s URL created by OpenShift to access the application from a web browser window.
 
 ----
 
 `Step 2a:` Click on the icon at the top right of the ring in the application visualization, as shown in the figure below, to quickly access the URL for the deployed application in the Topology view.
 
-![App Running](..\assets\app-running.png)
+![App Running](../assets/app-running.png)
 
 Make sure the ring surrounding the Python logo is dark blue.
 
 `Step 2b:` Click on the Open URL icon as shown in the figure above.
 
 Clicking the icon will open a new tab in your browser that displays a blog website page, as shown in the figure below.
 
-![Blog Web Site](..\assets\blog-web-page.png)
+![Blog Web Site](../assets/blog-web-page.png)
 
 This website is driven by the Python application you built from the source code in GitHub and deployed using the OpenShift web console.
 
@@ -50,4 +50,4 @@ This website is driven by the Python application you built from the source code
 You've successfully built and deployed an application from source code using the OpenShift web console.
 
 ----
-**NEXT:** Deleting the deployment from the command line using the OpenShift CLI Tool
+**NEXT:** Deleting the deployment from the command line using the OpenShift CLI Tool
diff --git a/...s/using-the-cluster-deploying-python/08-07-triggering-a-new-build/assignment.md b/...s/using-the-cluster-deploying-python/08-07-triggering-a-new-build/assignment.md
@@ -45,11 +45,11 @@ You can also trigger a build from within the OpenShift web console. Let's execut
 
 `Step 2b:` Click the **Start build** item in the drop-down menu on the right side of the build page, as shown in the figure below.
 
-![Build](..\assets\builds-menu.png)
+![Build](../assets/builds-menu.png)
 
 You'll see results similar to the figure shown below.
 
-![Build results](..\assets\start-build-results.png)
+![Build results](../assets/start-build-results.png)
 
 ---
 
@@ -196,7 +196,7 @@ The ``--wait`` option is supplied to indicate that the command should only retur
 
 `Step 9:` Go to the web page where the example code is running. You will see that the color of the header section on the web page has changed to blue, as shown in the figure below.
 
-![Blue Build](..\assets\blue-build.png)
+![Blue Build](../assets/blue-build.png)
 
 When you use the ``--from-dir=.`` option with ``oc start-build``, the contents from the current working directory will only be used for that one build.
 

diff --git a/instruqt-tracks/using-the-cluster-deploying-python/track.yml b/instruqt-tracks/using-the-cluster-deploying-python/track.yml
@@ -31,10 +31,10 @@ owner: openshift
 developers:
 - [email protected]
 - [email protected]
-- [email protected]
 - [email protected]
-- [email protected]
 - [email protected]
+- [email protected]
+- [email protected]
 idle_timeout: 400
 timelimit: 3600
 sandbox_preset: openshift-4-12
@@ -44,4 +44,5 @@ lab_config:
   position: right
   feedback_recap_enabled: true
   loadingMessages: true
-checksum: "9054786381529677514"
+  hideStopButton: false
+checksum: "15051188449312794897"