Changes between Version 4 and Version 5 of restream
- Timestamp:
- Oct 27, 2016, 3:22:09 PM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
restream
v4 v5 4 4 5 5 Restream allows us to take a jitsi meeting and send the video and audio to our icecast servers, which are designed to handle hundreds of simultaneous connections. 6 7 You can use restream to simply broadcast a jitsi meet video conference, or you can use it to setup a dedicated page on https://participate.mayfirst.org/ that incorporates both the icecast stream and the jitsi chat. 6 8 7 9 This page documents how to use restream. … … 11 13 == Setup == 12 14 15 === Just send to icecast === 16 13 17 First, ensure you have joined the jitsi meeting using the browser you intend to use for your own participation. This step ensures you are granted moderator rights. 14 18 15 Next, login to dee.mayfirst.org as root:19 Login to dee.mayfirst.org as root: 16 20 17 21 {{{ … … 19 23 }}} 20 24 21 Next, launch the stream specifying the final part of the jitsi URL. In other words, if your jitsi meeting is at https://meet.mayfirst.org/mfpl, you would specify "mfpl" as the only argument, e.g.:25 Launch the stream specifying the final part of the jitsi URL. In other words, if your jitsi meeting is at https://meet.mayfirst.org/mfpl, you would specify "mfpl" as the only argument, e.g.: 22 26 23 27 {{{ … … 33 37 docker rm mfpl 34 38 }}} 39 40 === The full deal === 41 42 If you want to create a special room for being to both watch the icecast stream and participate in the chat (and even present the agenda), you can use the `restream-setup` command. 43 44 Specify the start time, stop time and the name like so: 45 46 {{{ 47 restream-setup now "1 hour" mymeeting 48 }}} 49 50 Or... 51 52 {{{ 53 restream-setup "2016-02-12 09:00" "2016-02-12 11:00" checkin 54 }}} 55 56 Then, `restream-setup` will output details about your meeting, including the URL to send people to watch (which will be `https://participate.mayfirst.org/<name>). 57 58 A once a minute cron job takes care of starting and stopping your docker instance (that way we won't accidentally leave CPU hungry processes running). 35 59 36 60 == How it works ==