VeerMuchandi · Mar 26, 2019 · May 30, 2019 · Jun 19, 2019 · Jun 19, 2019 · Jun 19, 2019
Showing with 30 additions and 3 deletions.

+1 −1 CreatingFactory.md

+1 −1 DebuggingUsingCodeReadyWorkspaces.md

+1 −1 EditCodeUsingCodeReadyWorkspaces.md

+27 −0 readme.md
diff --git a/CreatingFactory.md b/CreatingFactory.md
@@ -1,6 +1,6 @@
 ## Creating Factory
 
-So far we created a workspace in CodeReady Workspaces with certain stack, imported code, and configured our workspace with maven configuration, added maven commands for `build and run` and `debug`, added remote debug configuration etc. This is some good amount of work and expecting every developer on the team that is working on our project/code is both time consuming and error prone. Onboarding developers has always been a challenge. 
+So far we created a workspace in CodeReady Workspaces with a certain stack, imported code, and configured our workspace with maven configuration, added maven commands for `build and run` and `debug`, added remote debug configuration etc. This is some good amount of work and expecting that setup from every developer on the team that is working on our project/code is both time consuming and error prone. Onboarding developers has always been a challenge. 
 
 How about a simple link that can be shared with our team members so that this configuration can be repeated? 
 

diff --git a/DebuggingUsingCodeReadyWorkspaces.md b/DebuggingUsingCodeReadyWorkspaces.md
@@ -18,7 +18,7 @@ You will notice that this will change the view to Java view as below. You may ha
 
 ### Add Debug Maven Command
 
-We will use the same approach like how we added the 
+We will use the same approach like how we added the `build and run` command earlier
 
 * Switch to command view on the project explorer
 * Click on the `+` symbol next to `Debug` and select `Maven` type

diff --git a/EditCodeUsingCodeReadyWorkspaces.md b/EditCodeUsingCodeReadyWorkspaces.md
@@ -32,7 +32,7 @@ Let us create a new Workspace.
 * **RAM:** You can choose the RAM size for the dev-machine. We can leave the default `2GB`
 * **Projects:** Click on `Add or Import Project`. Choose `Git` option and paste the URL for the GitRepo where your code was created by the Launcher.
 ![](./images/2.CodeReady.png)
-* Create on the `Create and Open` button. This will start launching a new workspace.
+* Click on the `Create and Open` button. This will start launching a new workspace.
 
 ![](./images/3.CodeReady.png)
 

diff --git a/readme.md b/readme.md
@@ -14,3 +14,30 @@
 * [Debugging code using CodeReady workspaces](DebuggingUsingCodeReadyWorkspaces.md)
 * [Creating Factories](CreatingFactory.md) 
 
+### Notes for RHPDS Users
+
+The labs above assume Launcher and CodeReady Workspaces are deployed on the same OpenShift cluster, and that
+Launcher is configured to deploy to an OpenShift cluster. However, the RHPDS catalog item does not yet
+deploy a version of Launcher, and it does not provide OpenShift console access. Instead, the Red Hat Developers
+Launcher can be used to generate and download code. Deployment of that code to an OpenShift cluster
+is optional and is not required by CodeReady Workspaces.
+
+RHPDS users can work through the labs above, additionally doing the following:
+
+1. Skip the steps for installing CodeReady Workspaces and Launcher. CodeReady Workspaces has already been installed
+for you and instructions to access it have been provided via email
+
+2. Open and login to the [Red Hat Developers Launcher](http://developers.redhat.com/launch), and follow
+the steps to create a backend application as detailed in [Using Launcher to generate code](GenerateCodeUsingLauncher.md)
+
+3. After configuring the project in Launcher, click the `Download` button
+
+4. In your personal GitHub account, create a repository with the code you downloaded. You will check out this git repository
+to CodeReady Workspaces in the next lab
+
+5. Optionally, if you have access to an OpenShift cluster, deploy the code from the repo you just created using the Java S2I
+image
+
+6. Optionally, create a web hook in GitHub with the secret provided in the OpenShift build to trigger new builds on code push
+
+7. Continue on with the next lab, [Editing code using CodeReady workspaces](EditCodeUsingCodeReadyWorkspaces.md)