Differences

This shows you the differences between two versions of the page.

--- software:relive [2016/07/03 19:09] – andi
+++ software:relive [2023/06/09 13:12] – andi
@@ Line 1: / Line 1: @@
-= Relive
+= HLS Relive
-Documentation for the relive system is contained within its git repo: ''git@c3voc.de:hls-relive''
+Documentation for the relive system is contained within its git repo ''git@c3voc.de:hls-relive'' mirrored at https://github.com/voc/hls-relive -> README.md
-== mini howto
+It's currently deployed at live.alb:/home/relive/git/
-  * ''[9|13:20] <florolf> bjoern: ich hab relive gerade angeworfen. das beschraenkt sich auf config bauen und dann scheduler.pl in 'nem screen starten (RELIVE_PROJECT=configname perl scheduler.pl ../data/conferencename/schedule.xml)''
-  * ''[9|13:22] <florolf> fuer den downloader von der streaming-ws waren noch die permissions auf das conference-directory falsch''
-  * ''[9|13:26] <florolf> bjoern: die streaming-website hat einen cronjob, der sich das relive-manifest runterzieht. das iteriert aber automatisch ueber alle existierenden konferenzen. pro konferenz muss da nur die download.sh richtig angelegt werden (siehe existierende configs auf lb1)''
-== Anleitung (in progress)
+== Setting up Relive in the VOC setup
-  ssh voc@live.ber.c3voc.de
+Login to server
-  sudo su relive
+  ssh relive@relive.c3voc.de
-  screen -x
+  cd git
-  # weiter siehe oben
+  screen -dR
+  - Create an appropriate config for your event in `live.alb:/home/relive/git/configs`
+    - either by using `./gen_event_config.py <conference slug>`, or
+    - manually: copy `cfg.example`, look at other files in that directory, or in the `old/` subdirectory for inspiration. The filename will be used as the conference name from here on.
+  - After a minute, a cronjob will run and download the schedule, etc. (If you are impatient, you can run `/home/relive/git/scripts/foreach-project.sh /home/relive/git/scripts/get-fahrplan.sh` manually)
+  - Start the scheduler (run as user relive, inside of a screen/tmux session): `./launcher.sh <conference slug>`
+  - In the streaming-website configuration, set ''RELIVE_JSON'' to point to ''%%http://relive.c3voc.de/relive/<conference slug>/index.json%%''
+Note that the ''index.json'' file is also only regenerated periodically, so it might be a minute or two before that URL actually works.
+== Relive integration in media.ccc.de (voctoweb)
+When an event in voctoweb has no recordings, voctoweb will try to find the corresponding relive recording. This only works if the conference acronym matches the acronym used in the relive system.
+To use this feature, first create the conference in voctoweb and in c3tracker. In theory there are multiple variants, but this one is the one we currently use:
+* To enable this workflow for you conference, enable the "releasing-relive-voctoweb" worker group which is handled by a modified version of CRS worker `script-A` living in a screen (user voc).
+  * TODO: Create systemd timer for this.
+* [[https://github.com/voc/voctopublish/blob/feature/relive/voctopublish/create-event-by-ticket.py|create-event-by-ticket.py]] is able to create an event in voctoweb, based on the CRS Ticket ID.
+* This script can be called during any state transition, we currently use `scheduled` -> `recording` of the recording ticket
+If you need re-create the session, run following commands:
+```
+ssh voc@releasing.c3voc.de
+screen -x
+cd /opt/crs/tools/tracker3.0
+source tracker-profile-relive.sh
+export LOCALFILE=tracker-profile-relive.sh
+./bin/crs_run script-A-recording+relive-scheduler.pl
+```
+== README
+Please read the [[https://github.com/voc/hls-relive/blob/master/README.md|README]] in the repository, it is being kept up to date with regard to the general behavior of the relive system.