@@ -72,11 +72,11 @@ The following gives an overview of how the Streaming Media Service is deployed a
### How and where the Streaming Media Service is deployed
The Streaming Media Service application is deployed using RPM packages. These are built by Gitlab CI in the [Application Server repository](https://gitlab.developers.cam.ac.uk/uis/sysdev/devgroup/sms/sms). These can be copied to the [Bes RPM package repository](bes.csi.cam.ac.uk) run by infra-sas@uis by following these [instructions](https://wiki.cam.ac.uk/ucs/Bes_-_Managed_Installation_Service#How_to_add_SLES_10.2F11_or_RHEL_.28S.29RPMS_to_Bes). As a last resort RPMs can be manually copied and installed.
The Streaming Media Service application is deployed using RPM packages. These are built by Gitlab CI in the [Application Server repository](https://gitlab.developers.cam.ac.uk/uis/sysdev/devgroup/sms/sms). These can be copied to the [Bes RPM package repository](https://bes.csi.cam.ac.uk) run by infra-sas@uis by following these [instructions](https://wiki.cam.ac.uk/ucs/Bes_-_Managed_Installation_Service#How_to_add_SLES_10.2F11_or_RHEL_.28S.29RPMS_to_Bes). As a last resort RPMs can be manually copied and installed.
### Deploying a new release
Once the RPM packages are added to the [Bes RPM package repository](bes.csi.cam.ac.uk) installation is simply a matter of running `zypper up` as root.
Once the RPM packages are added to the [Bes RPM package repository](https://bes.csi.cam.ac.uk) installation is simply a matter of running `zypper up` as root.
