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 [2023/06/09 13:12] – andisoftware:relive [2024/12/20 22:26] (current) – andi
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 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)   - 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 30: Line 30:
  
 * 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).  * 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. * [[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 * This script can be called during any state transition, we currently use `scheduled` -> `recording` of the recording ticket
 +  * 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.
  
 If you need re-create the session, run following commands: If you need re-create the session, run following commands:
Line 49: 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. 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)
  • software/relive.1686309177.txt.gz
  • Last modified: 2023/06/09 13:12
  • by andi