Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updated the bbb-webhooks documentation. Ensuring the configuration file gets ignored. #11308

Merged
merged 2 commits into from Feb 8, 2021

Conversation

AlexJezior
Copy link
Contributor

The current bbb-webhooks readme.md documentation doesn't accurately tell how to get the bbb-webhooks configured for custom development, and release procedures. Updates are my venture into configuring webhooks for my own personal use, while providing documentation to help others in the future from having to start a new topic in regards, on the bigbluebutton-dev group forum.

@ffdixon ffdixon requested a review from fcecagno February 7, 2021 22:46
Copy link
Member

@fcecagno fcecagno left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good job @AlexJezior, would you please take a look at my comments? Thanks!


This is a node.js application that listens for all events on BigBlueButton and sends POST requests with details about these events to hooks registered via an API. A hook is any external URL that can receive HTTP POST requests.

You can read the full documentation at: https://docs.bigbluebutton.org/dev/webhooks.html
You can read the full documentation at: http://docs.bigbluebutton.org/labs/webhooks.html
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The original URL was correct.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interesting! I don't even recall making this change; should be resolved now.

getRaw: false
}
]
```
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Two suggestions:

  • permanentURLs is above the hooks attribute, so I suggest to modify the sentence to something like "Locate hooks.permanentURLs on config/default.yml and modify it as follows:"
  • use the yaml syntax as follows:
permanentURLs:
  - url: 'https://staging.example.com/webhook-post-route'
    getRaw: false
  - url: 'https://app.example.com/webhook-post-route'
    getRaw: false

sudo make install
~~~
If you are editing these permanent urls after they have already been committed to the application once, you may need to flush the redis database in order for adjustments to these permanent hooks to get picked up by your application. Use the following command to do so:
- `redis-cli flushall`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add a warning mentioning that all events will be wiped from redis, which means that no ongoing recording will be processed.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great idea!

Comment on lines 5 to 6
config_local.coffee
config_local.js
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would you please remove these two, since they are no longer used?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Almost did this originally, but wasn't sure if there would be potential lingering configurations floating around out there that we would still like to keep out of the repository.

Copy link
Member

@fcecagno fcecagno left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for your contribution.

@antobinary
Copy link
Member

@AlexJezior Thank you for your contribution! Could you please confirm you have filled out a CLA? https://docs.bigbluebutton.org/support/faq.html#why-do-i-need-to-sign-a-contributor-license-agreement-to-contribute-source-code ?

@AlexJezior
Copy link
Contributor Author

@fcecagno @antobinary My pleasure to help!

I did fill out and email the CLA yesterday to the ffdixon@bigbluebutton.org email address.

@fcecagno fcecagno merged commit 23c34e8 into bigbluebutton:develop Feb 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants