Update internal README with new command

Author: shanereetz

README.md

@@ -17,6 +17,31 @@ The project includes:
 
 Through this project, users can interact with Isaac Sim and Isaac Lab purely from a web browser, with one tab running Visual Studio Code and terminal commands such as headless Isaac Sim instances, and another tab representing the Kit App Streaming and user interface for Isaac Sim.
 
+### Quickstart Guide
+This guide will get you started with a Visual Studio Code instance with Isaac Lab preinstalled, and an in-browser user interface provided by Kit App Streaming.
+
+1. Click the Deploy Now button below
+[![ Click here to deploy.](https://brev-assets.s3.us-west-1.amazonaws.com/nv-lb-dark.svg)](https://brev.nvidia.com/launchable/deploy?launchableID=env-31ezDWyp4LvtDQr5rUhAWOUMFhn)
+
+2. Wait for the the instance to be fully ready on Brev. The first time, this will take a while. Wait for it to be running, built, and for the setup script is complete.
+3. Scroll down to the TCP/UDP ports section of the Brev instance page.
+4. Click the link associated with port 80 - this will take you to Visual Studio Code Server.
+5. The default password is `password`. This can be modified.
+6. Continue with the [README.md](https://github.com/isaac-sim/isaac-launchable/blob/main/isaac-lab/vscode/README.md) instructions inside Visual Studio code. A summary is provided below.
+
+Now you can run Isaac Lab as normal, unless you need to see the UI of Isaac Sim (for example, when evaluating a policy)
+To do this:
+1. Add these additional arguments to the Isaac Lab command `--kit_args="--no-window --enable omni.kit.livestream.webrtc"`.
+2. Open a new tab in your browser.
+3. Visit the same address as the Visual Studio Code server, but with a `/viewer` path appended.
+
+Example: 
+
+VSCode - `ec2.something.something.amazonaws.com` at port 80
+
+Isaac Sim UI - `ec2.something.something.amazonaws.com/viewer`
+
+
 ### Required Ports
 The following ports need to be opened, for both the Visual Studio container and for Kit App Streaming.
 ```

isaac-lab/vscode/Dockerfile

@@ -15,6 +15,7 @@
 FROM nvcr.io/nvidia/isaac-lab:2.2.0
 
 USER root
+ENV OMNI_KIT_ALLOW_ROOT=1
 
 RUN apt update && \
     apt install -y \

isaac-lab/vscode/README.md

@@ -3,27 +3,28 @@
 This project provides a simple way to interact with Isaac Lab, and Isaac Sim, either on the cloud or locally.
 See the [project repo](https://github.com/isaac-sim/isaac-launchable) for more detaild instructions, but below is a quickstart guide.
 
-## Running Isaac Sim
+## Running Isaac Lab
 
-You can run the streaming Isaac Sim application at anytime with the following command:
+You can run any of the Issac Lab scripts with the streaming Isaac Sim experience with the following command:
 
 ```console
-isaacsim isaacsim.exp.full.streaming.kit --no-window
+./isaaclab.sh -p "scripts/tutorials/00_sim/create_empty.py" --kit_args="--no-window --enable omni.kit.livestream.webrtc"
 ```
 
 Then, in a separate browser window, open `https://{your instance's address}/viewer`.
 
-For example, if this is run on a local computer: `127.0.0.1/viewer`
-If this is run on an AWS instance, the address may be more like: 
+To run any other Isaac Lab commands, simply append those same arguments as shown above: `--kit_args="--no-window --enable omni.kit.livestream.webrtc"`
 
-## Running Isaac Lab
+## Running Isaac Sim
 
-You can run any of the Issac Lab scripts with the streaming Isaac Sim experience with the following command:
+You can run the streaming Isaac Sim application at anytime with the following command:
 
 ```console
-./isaaclab.sh -p "scripts/tutorials/00_sim/create_empty.py" --kit_args="--no-window --enable omni.kit.livestream.webrtc"
+/workspace/isaaclab/_isaac_sim/isaac-sim.sh --no-window --enable omni.kit.livestream.webrtc
 ```
 
 Then, in a separate browser window, open `https://{your instance's address}/viewer`.
 
-To run any other Isaac Lab commands, simply append those same arguments as shown above: `--kit_args="--no-window --enable omni.kit.livestream.webrtc"`
+For example, if this is run on a local computer: `127.0.0.1/viewer`
+If this is run on an AWS instance, the address may be more like: 
+`http://ec2-00-00-000-000.compute-1.amazonaws.com/viewer`