Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
software:relive [2019/03/13 17:10] – andi | software:relive [2024/01/03 16:49] (current) – [Relive integration in media.ccc.de (voctoweb)] andi | ||
---|---|---|---|
Line 3: | Line 3: | ||
Documentation for the relive system is contained within its git repo '' | Documentation for the relive system is contained within its git repo '' | ||
- | It's currently deployed at live.ber:/ | + | It's currently deployed at live.alb:/ |
== Setting up Relive in the VOC setup | == Setting up Relive in the VOC setup | ||
Login to server | Login to server | ||
- | ssh relive@live.ber.c3voc.de | + | ssh relive@relive.c3voc.de |
cd git | cd git | ||
screen -dR | screen -dR | ||
- | - Create an appropriate config for your event in `live.ber:/ | + | - Create an appropriate config for your event in `live.alb:/ |
- either by using `./ | - either by using `./ | ||
- manually: copy `cfg.example`, | - manually: copy `cfg.example`, | ||
- After a minute, a cronjob will run and download the schedule, etc. (If you are impatient, you can run `/ | - After a minute, a cronjob will run and download the schedule, etc. (If you are impatient, you can run `/ | ||
- Start the scheduler (run as user relive, inside of a screen/tmux session): `./ | - Start the scheduler (run as user relive, inside of a screen/tmux session): `./ | ||
- | - In the streaming-website configuration, | + | - In the streaming-website configuration, |
Note that the '' | Note that the '' | ||
+ | |||
+ | |||
+ | == 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 " | ||
+ | * [[https:// | ||
+ | * 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: | ||
+ | |||
+ | |||
+ | ``` | ||
+ | ssh voc@releasing.c3voc.de | ||
+ | screen -x | ||
+ | cd / | ||
+ | source tracker-profile-relive.sh | ||
+ | export LOCALFILE=tracker-profile-relive.sh | ||
+ | ./ | ||
+ | ``` | ||
+ | |||
== README | == README | ||
Please read the [[https:// | Please read the [[https:// | ||
+ | |||
+ | == FAQ | ||
+ | |||
+ | The `/ | ||
+ | * simply rename or remove the file, it will be generated in the next run (or trigger it manually) |