Vip: Redeploying Vip after a new build

Currently, all the below takes place on Krypton (192.168.40.60)

1. Shut down pixel streaming with sudo systemctl stop signalling

2. Shut down all currently running instances of VIP by cding to home cd ~ and running ./run_vip_instances.sh stop

3. cd /opt/vip/build and remove old versions of vip with sudo rm -r Vip_0.9 and rm Vip_0.9.zip

4. Build the project in UE5 and then Zip the built project folder

5. Using filezilla or any other protocol for transfering files over ssh, move the zip into Krypton (e.g. into the Downloads folder)

6. Move the file from ~/Downloads into /opt/vip/build using: sudo mv ~/Downloads/Vip_0.9.zip /opt/vip/build/

7. cd into the dir cd /opt/vip/build

8. unzip with sudo unzip Vip_0.9.zip -d Vip_0.9

9. check it worked with ls /opt/vip/build/Vip_0.9

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)

sed -i 's|^UE_BIN=".*"|UE_BIN="/opt/vip/build/Vip_0.9/Vip_0.9/Linux/VIP.sh"|' ~/run_vip_instances.sh
sudo chmod +x /opt/vip/build/Vip_0.9/Vip_0.9/Linux/VIP.sh \
              /opt/vip/build/Vip_0.9/Vip_0.9/Linux/VIP/Binaries/Linux/VIP-Linux-Shipping
~/run_vip_instances.sh start 1

if the one instance booted through the script above starts you're almost good to go

11. Kill the test instance at cd ~ with ./run_vip_instances.sh stop

12. Fix some permissions

• sudo chown nathan:nathan /opt/vip/build/Vip_0.9/Vip_0.9/Linux/VIP/Binaries/Linux/VIP-Linux-Shipping
• sudo chmod 755 /opt/vip/build/Vip_0.9/Vip_0.9/Linux/VIP/Binaries/Linux/VIP-Linux-Shipping
• sudo chown -R nathan:nathan /opt/vip/build/Vip_0.9

13. Redeploy VIP at cd ~ with ./run_vip_instances.sh start 18

14. Wait for all instances to come online. You can monitor this with nvtop and watch for GPU usage to stabilise across all gpus

15. Redeploy pixel streaming with sudo systemctl start signalling