Felipe Cecagno d8b3375f48 we don't want to archive recordings in which there's no mark to start the recording; it would be the same as if the meeting would be created with record=false - the only difference is that the events are archived to recordings/raw/meeting_id/events.xml, and the recorded .done flag is created as well		2013-10-02 14:18:26 -03:00
..
archive	we don't want to archive recordings in which there's no mark to start the recording; it would be the same as if the meeting would be created with record=false - the only difference is that the events are archived to recordings/raw/meeting_id/events.xml, and the recorded .done flag is created as well	2013-10-02 14:18:26 -03:00
process	- make script dir part of core instead of separate bin dir for easier triggering of build/packaging of bbb-record-core package	2011-05-22 17:10:22 -04:00
publish	- make script dir part of core instead of separate bin dir for easier triggering of build/packaging of bbb-record-core package	2011-05-22 17:10:22 -04:00
sanity	remove events and files for webcam streams with length zero	2013-07-15 15:22:39 -05:00
bbb-rap.sh	Update license.	2012-09-04 16:42:13 -05:00
bigbluebutton.yml	Fix playback host address	2013-07-29 16:28:04 +00:00
cleanup.rb	Update license.	2012-09-04 16:42:13 -05:00
rap-worker.rb	rap-worker now keeps track of the processing time of a recording; a file called processing_time is generated during the process phase, and this information is added to metadata.xml when the recording is published - this information isn't retrieved by getRecordings because no modification was done on bbb-web to include this information, but at least it's there so the sysadmin can check how long does a recording take to get processed	2013-06-13 17:13:20 -03:00