software:relive

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
software:relive [2024/01/03 15:49] – [Relive integration in media.ccc.de (voctoweb)] andisoftware:relive [2026/07/26 22:17] (current) – external edit 127.0.0.1
Line 1: Line 1:
-= HLS Relive+# 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 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
Line 6: Line 6:
  
  
-== Setting up Relive in the VOC setup+## Setting up Relive in the VOC setup
  
 Login to server  Login to server 
Line 15: Line 15:
   - Create an appropriate config for your event in `live.alb:/home/relive/git/configs`   - Create an appropriate config for your event in `live.alb:/home/relive/git/configs`
     - either by using `./gen_event_config.py <conference slug>`, or     - 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 if you 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)   - 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>`   - Start the scheduler (run as user relive, inside of a screen/tmux session): `./launcher.sh <conference slug>`
Line 23: Line 23:
  
  
-== Relive integration in media.ccc.de (voctoweb)+## 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.  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. 
Line 46: Line 46:
 ``` ```
  
-== README+## 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. 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+## FAQ
  
 The `/video/relive/<conference>/<id>/index.m3u8` is empty/broken, how can I regenerate the file? 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)   * 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.
 +
  • software/relive.1704296968.txt.gz
  • Last modified: 2024/01/03 15:49
  • by andi