Updated signal server sections of guides

Updated the setup signalling server sections of all the guides to use the new universal signalling server scripts.

Author: MWillWallT

Pixel Streaming on AWS (Linux).md

@@ -180,13 +180,11 @@ This is definitely not a mandatory step, and if you just want to do a quick test
 
 In the terminal window that’s in the bash directory, enter `ls` to see the directories contents.
 
-You should see a variety of `.sh` files, many of them run on each other so don’t fret!
+You should see a variety of `.sh` files, you can always refer to the README in the folder to see what each file does.
 
-Type `./setup.sh`
+Type `./setup.sh`, this will install all the pre-requisites to run a signalling server!
 
-You may get an error message warning of a vulnerability enter `npm audit fix` to rectify.
-
-Type `./runAWS_WithTurn.sh` 
+Once that is done type `./Start_WithTURN_SignallingServer.sh` 
 
 If you have done all of the above correctly, you should see:
 ```

Pixel Streaming on AWS (Windows).md

@@ -192,10 +192,18 @@ Head to your projects cmd directory, found in:
 WindowsNoEditor\Samples\PixelStreaming\WebServers\SignallingWebServer\platform_scripts\cmd
 ```
 
-You'll see a number of .bat files in here, but don't worry! Many of them run on each other.
+You'll see a variety of files in here, you can always refer to the README in this folder to see what each of them do. But our first step is to install the pre-requisites to run a signalling server!
 
-Go ahead and run `runAWS_WithTurn.bat`.
-This will open your signalling server window and run the setup.bat, which checks that npm is installed. Once that is verified, the output should end in:
+1. Open your start menu and search for Powershell
+2. Right click Windows Powershell and run as administrator
+3. In your powershell window enter `cd PATH\WindowsNoEditor\Samples\PixelStreaming\WebServers\SignallingWebServer\platform_scripts\cmd` (Replacing PATH with your own file path)
+4. Enter `.\setup.ps1` 
+
+This should automatically install all the required components to run your signalling server. 
+Furthermore, now that you have done this, you do not need powershell to be elevated, so to run the other scripts, you can simply right click them and select "Run with Powershell"
+
+Go ahead and run `Start_WithTURN_SignallingServer.ps1`.
+This will open your signalling server window. Once that is done, the output should end in:
 
 ```
 00:36:55.279 WebSocket listening to Streamer connections on :8888

Pixel Streaming on Azure (Linux).md

@@ -233,13 +233,11 @@ This is definitely not a mandatory step, and if you just want to do a quick test
 
 In the terminal window that’s in the bash directory, enter `ls` to see the directories contents.
 
-You should see a variety of `.sh` files, many of them run on each other so don’t fret!
+You should see a variety of `.sh` files, you can always refer to the README in the folder to see what each file does.
 
-Type `./setup.sh`
+Type `./setup.sh`, this will install all the pre-requisites to run a signalling server!
 
-You may get an error message warning of a vulnerability enter `npm audit fix` to rectify.
-
-Type `./runAWS_WithTurn.sh` 
+Once that is done type `./Start_WithTURN_SignallingServer.sh` 
 
 If you have done all of the above correctly, you should see:
 ```

Pixel Streaming on Azure (Windows).md

@@ -177,10 +177,18 @@ Head to your projects cmd directory, found in:
 WindowsNoEditor\Samples\PixelStreaming\WebServers\SignallingWebServer\platform_scripts\cmd
 ```
 
-You'll see a number of .bat files in here, but don't worry! Many of them run on each other.
+You'll see a variety of files in here, you can always refer to the README in this folder to see what each of them do. But our first step is to install the pre-requisites to run a signalling server!
 
-Go ahead and run `runAWS_WithTurn.bat`.
-This will open your signalling server window and run the setup.bat, which checks that npm is installed. Once that is verified, the output should end in:
+1. Open your start menu and search for Powershell
+2. Right click Windows Powershell and run as administrator
+3. In your powershell window enter `cd PATH\WindowsNoEditor\Samples\PixelStreaming\WebServers\SignallingWebServer\platform_scripts\cmd` (Replacing PATH with your own file path)
+4. Enter `.\setup.ps1` 
+
+This should automatically install all the required components to run your signalling server. 
+Furthermore, now that you have done this, you do not need powershell to be elevated, so to run the other scripts, you can simply right click them and select "Run with Powershell"
+
+Go ahead and run `Start_WithTURN_SignallingServer.ps1`.
+This will open your signalling server window. Once that is done, the output should end in:
 
 ```
 00:36:55.279 WebSocket listening to Streamer connections on :8888

Pixel Streaming on GCP (Linux).md

@@ -213,13 +213,11 @@ Change your directory on the instance to your signal server files, the directory
 
 Now that you're in the bash directory, enter `ls` to see the directories contents.
 
-You should see a variety of `.sh` files, many of them run on each other so don’t fret!
+You should see a variety of `.sh` files, you can always refer to the README in the folder to see what each file does.
 
-Type `./setup.sh -y`
+Type `./setup.sh`, this will install all the pre-requisites to run a signalling server!
 
-This will install a variety of required elements the signalling server needs to function.
-
-Once complete, you can start the signalling server by running: `./Start_SignallingServer.sh` 
+Once that is done type `./Start_WithTURN_SignallingServer.sh` 
 
 If you have done all of the above correctly, you should see:
 ```
@@ -228,9 +226,7 @@ WebSocket listening to Players connections on :80
 Http listening on *: 80
 ```
 
-If you see the above, then your signalling server is up and running! 
-
-With all of this set up, you now have a signalling server ready!
+If you see the above, then your signalling server is up and running!
 
 ## Running Your Application
 

Pixel Streaming on GCP (Windows).md

@@ -170,10 +170,18 @@ Head to your projects cmd directory, found in:
 WindowsNoEditor\Samples\PixelStreaming\WebServers\SignallingWebServer\platform_scripts\cmd
 ```
 
-You'll see a number of .bat files in here, but don't worry! Many of them run on each other.
+You'll see a variety of files in here, you can always refer to the README in this folder to see what each of them do. But our first step is to install the pre-requisites to run a signalling server!
 
-Go ahead and run `runAWS_WithTurn.bat`.
-This will open your signalling server window and run the setup.bat, which checks that npm is installed. Once that is verified, the output should end in:
+1. Open your start menu and search for Powershell
+2. Right click Windows Powershell and run as administrator
+3. In your powershell window enter `cd PATH\WindowsNoEditor\Samples\PixelStreaming\WebServers\SignallingWebServer\platform_scripts\cmd` (Replacing PATH with your own file path)
+4. Enter `.\setup.ps1` 
+
+This should automatically install all the required components to run your signalling server. 
+Furthermore, now that you have done this, you do not need powershell to be elevated, so to run the other scripts, you can simply right click them and select "Run with Powershell"
+
+Go ahead and run `Start_WithTURN_SignallingServer.ps1`.
+This will open your signalling server window. Once that is done, the output should end in:
 
 ```
 00:36:55.279 WebSocket listening to Streamer connections on :8888