Differences

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

--- software:relive [2021/02/25 18:32] – [Setting up Relive in the VOC setup] lukas2511
+++ software:relive [2025/08/30 21:13] (current) – [Depublish] fix note about removing the HTML page jtbx
@@ Line 15: / Line 15: @@
   - 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.
+    - manually **(deprecated, do not use I you are not really know what you are doing)**: 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>`
@@ Line 29: / Line 29: @@
 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).
 * [[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
-* To enable this for you conference, enable the "releasing.c3voc.de-relive" worker group which is handled by a modified version of CRS worker `script-A` living in a screen (user voc).
+  * TODO: When we use this step, we should rename or migrate the deployment of of this script from releasing to storage, as it confuses tracker operators when the releasing host does the recording step.
-  * TODO: Create systemd timer for this.
 If you need re-create the session, run following commands:
@@ Line 50: / Line 49: @@
 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.
+== FAQ
+The `/video/relive/<conference>/<id>/index.m3u8` is empty/broken, how can I regenerate the file?
+  * simply rename or remove the file, it will be generated in the next run (or trigger it manually)
+== Depublish
+To de-publish a video, remove the folder with the video ID (`/video/relive/<conference>/<id>/`).
+Just renaming makes the video not playable, but the folder can still be found since dirlisting enabled at the CDN.
+The page at `https://streaming.media.ccc.de/<conference>/relive/<id>` should lead to a 404 after some cronjob ran.