Cleaning up documentation

README.md

@@ -93,7 +93,7 @@ After the launchsas.sh command is completed, use `docker ps` to list the running
 
 ### Sign In to SAS Studio
 
-Go to `http://<myhostname>:8081`, and then sign in with the sasdemo user ID and the sasdemo password to start using SAS Studio! 
+Go to `http://<myhostname>:8080`, and then sign in with the sasdemo user ID and the sasdemo password to start using SAS Studio! 
 
 <img src="docs/sas-logon-screen-sasdemo.png" alt="SAS Logon Screen" style="width: 80%; height: 80%; object-fit: contain;">
 

docs/usage.txt

@@ -42,6 +42,10 @@ Single Container
         For more information about using a mirror repository, see the Mirror Manager guide at
         https://support.sas.com/en/documentation/install-center/viya/deployment-tools/34/mirror-manager.html
 
+    --skip-mirror-url-validation
+        Skips validation of the URL specified in the --mirror-url argument.
+        Default: false
+
 
 Multiple Containers
 -------------------
@@ -116,7 +120,7 @@ Multiple Containers
         Default: false
 
     --skip-mirror-url-validation
-        Skips validating the mirror URL from the --mirror-url flag.
+        Skips validation of the URL specified in the --mirror-url argument.
         Default: false
 
     --skip-docker-url-validation

docs/wiki/Build-and-Run-SAS-Viya-Single-Container.md

@@ -310,7 +310,8 @@ sed -i 's|@REPLACE_ME_WITH_TAG@|<tag>|' ${PWD}/run/launchsas.sh
 cd run
 ```
 
-**Note:** Replace _<tag>_ with the value that you want to use.
+**Note:** Replace _\<tag\>_ with the value that you want to use.
+**Note:** If you used the auth-sssd addon or customised the user in the auth-demo addon, make sure to update the CASENV_ADMIN_USER to contain a valid username.
 
 When the script is run, it will create several directories for you. These are set up either to cause data to persist or to help with [configuration](#configuration). 
 

docs/wiki/Validating.md

@@ -75,7 +75,7 @@ If the image is not running, here are several recovery actions that you can perf
 
 To verify that the sas-programming process is running in Kubernetes, run the following command:
 
-`kubectl get -f sas-programming.yml`
+`kubectl get -f run/programming.yml`
 
 Here are typical results:
 
@@ -87,7 +87,7 @@ NAME                    READY   UP-TO-DATE   AVAILABLE   AGE
 sas-programming         1/1     1            1           11d
 ```
 
-**Tip:** Run the command from the directory where the sas-programming.yml file is located. For a programming-only deployment, the Kubernetes manifests are located at $PWD/builds/multiple/manifests/ and for a full deployment, the manifests are located at $PWD/builds/full/manifests/.
+**Tip:** Run the command from the directory where the programming.yml file is located. For a single image programming-only deployment, the Kubernetes manifests are located at $PWD/run/programming.yml. For a multiple image programming-only deployment, the manifests are lodated at $PWD/builds/multiple/manifests/kubernetes and for a full deployment, the manifests are located at $PWD/builds/full/manifests/kubernetes.
 
 If you do not get the results that you expect, run the following command to enable the DEBUG option to provide more information:
 

order.go

@@ -1682,6 +1682,9 @@ cp samples/viya-single-container/example_launchsas.sh run/launchsas.sh
 cd run
 sed -i 's|@REPLACE_ME_WITH_TAG@|%s|' launchsas.sh
 ./launchsas.sh
+
+Note: If you used the auth-sssd addon or customised the user in the auth-demo addon, 
+      make sure to update the CASENV_ADMIN_USER in run/launchsas.sh to contain a valid username.
 `, order.TagOverride)
 		order.WriteLog(true, nextStepInstructions)
 

samples/viya-single-container/example_launchsas.sh

@@ -17,6 +17,7 @@ run_args="
 --hostname $SAS_CONTAINER_NAME
 --env RUN_MODE=developer
 --env CASENV_ADMIN_USER=sasdemo
+--env CASENV_CAS_VIRTUAL_PORT=${SAS_HTTPS_PORT}
 --env CASENV_CAS_VIRTUAL_HOST=$(hostname -f)
 --env CASENV_CAS_VIRTUAL_PORT=${SAS_HTTP_PORT}
 --env CASENV_CASDATADIR=/cas/data