Blame

e88000 Anonymous 2026-04-14 00:11:01 1
# Vip: Redeploying Vip after a new build
19e000 Anonymous 2026-04-14 00:10:37 2
e88000 Anonymous 2026-04-14 00:11:01 3
Currently, all the below takes place on Krypton (192.168.40.60)
19e000 Anonymous 2026-04-14 00:10:37 4
e88000 Anonymous 2026-04-14 00:11:01 5
1. Shut down pixel streaming with `sudo systemctl stop signalling`
19e000 Anonymous 2026-04-14 00:10:37 6
e88000 Anonymous 2026-04-14 00:11:01 7
2. Shut down all currently running instances of VIP by cding to home `cd ~` and running `./run_vip_instances.sh stop`
19e000 Anonymous 2026-04-14 00:10:37 8
e88000 Anonymous 2026-04-14 00:11:01 9
3. `cd /opt/vip/build` and remove old versions of vip with `sudo rm -r Vip_0.9` and `rm Vip_0.9.zip`
19e000 Anonymous 2026-04-14 00:10:37 10
e88000 Anonymous 2026-04-14 00:11:01 11
4. Build the project in UE5 and then Zip the built project folder
19e000 Anonymous 2026-04-14 00:10:37 12
e88000 Anonymous 2026-04-14 00:11:01 13
5. Using filezilla or any other protocol for transfering files over ssh, move the zip into Krypton (e.g. into the Downloads folder)
19e000 Anonymous 2026-04-14 00:10:37 14
e88000 Anonymous 2026-04-14 00:11:01 15
6. Move the file from `~/Downloads` into `/opt/vip/build` using: `sudo mv ~/Downloads/Vip_0.9.zip /opt/vip/build/`
19e000 Anonymous 2026-04-14 00:10:37 16
e88000 Anonymous 2026-04-14 00:11:01 17
7. cd into the dir `cd /opt/vip/build`
19e000 Anonymous 2026-04-14 00:10:37 18
e88000 Anonymous 2026-04-14 00:11:01 19
8. unzip with `sudo unzip Vip_0.9.zip -d Vip_0.9`
19e000 Anonymous 2026-04-14 00:10:37 20
e88000 Anonymous 2026-04-14 00:11:01 21
9. check it worked with `ls /opt/vip/build/Vip_0.9`
19e000 Anonymous 2026-04-14 00:10:37 22
e88000 Anonymous 2026-04-14 00:11:01 23
10. run this script in the terminal to make sure the project is executable and that the instance booter is aware of the new folder (shouldnt be necessary if naming is all the same but do it just in case)
19e000 Anonymous 2026-04-14 00:10:37 24
25
```
e88000 Anonymous 2026-04-14 00:11:01 26
sed -i 's|^UE_BIN=".*"|UE_BIN="/opt/vip/build/Vip_0.9/Vip_0.9/Linux/VIP.sh"|' ~/run_vip_instances.sh
27
sudo chmod +x /opt/vip/build/Vip_0.9/Vip_0.9/Linux/VIP.sh \
28
/opt/vip/build/Vip_0.9/Vip_0.9/Linux/VIP/Binaries/Linux/VIP-Linux-Shipping
29
~/run_vip_instances.sh start 1
19e000 Anonymous 2026-04-14 00:10:37 30
31
```
e88000 Anonymous 2026-04-14 00:11:01 32
if the one instance booted through the script above starts you're almost good to go
33
34
11. Kill the test instance at `cd ~` with `./run_vip_instances.sh stop`
35
36
12. Fix some permissions
37
38
- `sudo chown nathan:nathan /opt/vip/build/Vip_0.9/Vip_0.9/Linux/VIP/Binaries/Linux/VIP-Linux-Shipping`
39
- `sudo chmod 755 /opt/vip/build/Vip_0.9/Vip_0.9/Linux/VIP/Binaries/Linux/VIP-Linux-Shipping`
40
- `sudo chown -R nathan:nathan /opt/vip/build/Vip_0.9`
41
42
13. Redeploy VIP at `cd ~` with `./run_vip_instances.sh start 18`
43
44
14. Wait for all instances to come online. You can monitor this with `nvtop` and watch for GPU usage to stabilise across all gpus
19e000 Anonymous 2026-04-14 00:10:37 45
e88000 Anonymous 2026-04-14 00:11:01 46
15. Redeploy pixel streaming with `sudo systemctl start signalling`