lino.jorzick/greenlight
1
0
Fork 0
forked from External/greenlight
Code Issues Pull Requests Projects Releases Wiki Activity

Add flag to use webhooks and API call to register a hook

Browse Source 
It almost works with webhooks now. Still TODO is:
* Remove the hook after the recording is published
* To process the publish_ended event from the webhooks either the webhook
  needs to include the metadata (currently it doesn't) or GreenLight has
  find out the meeting token without reading it from the metadata.
This commit is contained in:
Leonardo Crauss Daronco
2016-12-08 14:01:57 -02:00
parent 906b21ab0e
commit 09c30bb5bd
3 changed files with 59 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
sample.env
View File

@ -7,6 +7,16 @@ RAILS_ENV=development
BIGBLUEBUTTON_ENDPOINT=http://test-install.blindsidenetworks.com/bigbluebutton/
BIGBLUEBUTTON_SECRET=8cd8ef52e8e101574e400365b55e11a6
# If "true", GreenLight will register a webhook callback for each meeting
# created. This callback is called for all events that happen in the meeting,
# including the processing of its recording. These events are used to update
# the web page dynamically as things happen in the server.
# If not "true", the application will add a metadata to the meetings with this same
# callback URL. Scripts can then be added to BigBlueButton to call this callback
# URL and send specific events to GreenLight (e.g. a post publish script to warn
# the application when recordings are done).
GREENLIGHT_USE_WEBHOOKS=false
# OmniAuth
TWITTER_ID=
TWITTER_SECRET=