Skip to content

Commit 1dd2f6b

Browse files
committed
Updated signal server sections of guides
Updated the setup signalling server sections of all the guides to use the new universal signalling server scripts.
1 parent 89f7d62 commit 1dd2f6b

6 files changed

+43
-27
lines changed

Pixel Streaming on AWS (Linux).md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -180,13 +180,11 @@ This is definitely not a mandatory step, and if you just want to do a quick test
180180

181181
In the terminal window that’s in the bash directory, enter `ls` to see the directories contents.
182182

183-
You should see a variety of `.sh` files, many of them run on each other so don’t fret!
183+
You should see a variety of `.sh` files, you can always refer to the README in the folder to see what each file does.
184184

185-
Type `./setup.sh`
185+
Type `./setup.sh`, this will install all the pre-requisites to run a signalling server!
186186

187-
You may get an error message warning of a vulnerability enter `npm audit fix` to rectify.
188-
189-
Type `./runAWS_WithTurn.sh`
187+
Once that is done type `./Start_WithTURN_SignallingServer.sh`
190188

191189
If you have done all of the above correctly, you should see:
192190
```

Pixel Streaming on AWS (Windows).md

Lines changed: 11 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -192,10 +192,18 @@ Head to your projects cmd directory, found in:
192192
WindowsNoEditor\Samples\PixelStreaming\WebServers\SignallingWebServer\platform_scripts\cmd
193193
```
194194

195-
You'll see a number of .bat files in here, but don't worry! Many of them run on each other.
195+
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!
196196

197-
Go ahead and run `runAWS_WithTurn.bat`.
198-
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:
197+
1. Open your start menu and search for Powershell
198+
2. Right click Windows Powershell and run as administrator
199+
3. In your powershell window enter `cd PATH\WindowsNoEditor\Samples\PixelStreaming\WebServers\SignallingWebServer\platform_scripts\cmd` (Replacing PATH with your own file path)
200+
4. Enter `.\setup.ps1`
201+
202+
This should automatically install all the required components to run your signalling server.
203+
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"
204+
205+
Go ahead and run `Start_WithTURN_SignallingServer.ps1`.
206+
This will open your signalling server window. Once that is done, the output should end in:
199207

200208
```
201209
00:36:55.279 WebSocket listening to Streamer connections on :8888

Pixel Streaming on Azure (Linux).md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -233,13 +233,11 @@ This is definitely not a mandatory step, and if you just want to do a quick test
233233

234234
In the terminal window that’s in the bash directory, enter `ls` to see the directories contents.
235235

236-
You should see a variety of `.sh` files, many of them run on each other so don’t fret!
236+
You should see a variety of `.sh` files, you can always refer to the README in the folder to see what each file does.
237237

238-
Type `./setup.sh`
238+
Type `./setup.sh`, this will install all the pre-requisites to run a signalling server!
239239

240-
You may get an error message warning of a vulnerability enter `npm audit fix` to rectify.
241-
242-
Type `./runAWS_WithTurn.sh`
240+
Once that is done type `./Start_WithTURN_SignallingServer.sh`
243241

244242
If you have done all of the above correctly, you should see:
245243
```

Pixel Streaming on Azure (Windows).md

Lines changed: 11 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -177,10 +177,18 @@ Head to your projects cmd directory, found in:
177177
WindowsNoEditor\Samples\PixelStreaming\WebServers\SignallingWebServer\platform_scripts\cmd
178178
```
179179

180-
You'll see a number of .bat files in here, but don't worry! Many of them run on each other.
180+
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!
181181

182-
Go ahead and run `runAWS_WithTurn.bat`.
183-
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:
182+
1. Open your start menu and search for Powershell
183+
2. Right click Windows Powershell and run as administrator
184+
3. In your powershell window enter `cd PATH\WindowsNoEditor\Samples\PixelStreaming\WebServers\SignallingWebServer\platform_scripts\cmd` (Replacing PATH with your own file path)
185+
4. Enter `.\setup.ps1`
186+
187+
This should automatically install all the required components to run your signalling server.
188+
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"
189+
190+
Go ahead and run `Start_WithTURN_SignallingServer.ps1`.
191+
This will open your signalling server window. Once that is done, the output should end in:
184192

185193
```
186194
00:36:55.279 WebSocket listening to Streamer connections on :8888

Pixel Streaming on GCP (Linux).md

Lines changed: 4 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -213,13 +213,11 @@ Change your directory on the instance to your signal server files, the directory
213213

214214
Now that you're in the bash directory, enter `ls` to see the directories contents.
215215

216-
You should see a variety of `.sh` files, many of them run on each other so don’t fret!
216+
You should see a variety of `.sh` files, you can always refer to the README in the folder to see what each file does.
217217

218-
Type `./setup.sh -y`
218+
Type `./setup.sh`, this will install all the pre-requisites to run a signalling server!
219219

220-
This will install a variety of required elements the signalling server needs to function.
221-
222-
Once complete, you can start the signalling server by running: `./Start_SignallingServer.sh`
220+
Once that is done type `./Start_WithTURN_SignallingServer.sh`
223221

224222
If you have done all of the above correctly, you should see:
225223
```
@@ -228,9 +226,7 @@ WebSocket listening to Players connections on :80
228226
Http listening on *: 80
229227
```
230228

231-
If you see the above, then your signalling server is up and running!
232-
233-
With all of this set up, you now have a signalling server ready!
229+
If you see the above, then your signalling server is up and running!
234230

235231
## Running Your Application
236232

Pixel Streaming on GCP (Windows).md

Lines changed: 11 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -170,10 +170,18 @@ Head to your projects cmd directory, found in:
170170
WindowsNoEditor\Samples\PixelStreaming\WebServers\SignallingWebServer\platform_scripts\cmd
171171
```
172172

173-
You'll see a number of .bat files in here, but don't worry! Many of them run on each other.
173+
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!
174174

175-
Go ahead and run `runAWS_WithTurn.bat`.
176-
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:
175+
1. Open your start menu and search for Powershell
176+
2. Right click Windows Powershell and run as administrator
177+
3. In your powershell window enter `cd PATH\WindowsNoEditor\Samples\PixelStreaming\WebServers\SignallingWebServer\platform_scripts\cmd` (Replacing PATH with your own file path)
178+
4. Enter `.\setup.ps1`
179+
180+
This should automatically install all the required components to run your signalling server.
181+
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"
182+
183+
Go ahead and run `Start_WithTURN_SignallingServer.ps1`.
184+
This will open your signalling server window. Once that is done, the output should end in:
177185

178186
```
179187
00:36:55.279 WebSocket listening to Streamer connections on :8888

0 commit comments

Comments
 (0)