![]() ![]() We have a couple of ways for you to get up and started with the adapter below. * Required settings, unless running locally with testing defaults:īe aware you must add the bot's user as a member of the new private group(s)īefore it will respond. Name to ID source of messages in code (e.g Hubot) If the bot should respond in livechat rooms If the bot should reply / re-reply to edited messages If the bot can respond privately or only in the open The default room/s for the bot to listen in to (csv) Matching the credentials setup in Rocket.Chat Name in the platform (bot user must be created first) Local Rocketchat address (start before the bot) ![]() If the bot needs to listen to or make HTTP requests The minimum level of logs to output (error) Set to rocketchat (or pass as launch argument)Īn alternate name for the bot to respond to It has some additional configs, documented here. So the following are just some of those settings, The Rocket.Chat adapter implements the Rocket.Chat Node.js SDK to load all They would need to be set on server startup. In local development, the following can be set in an. More info in Hubot's own docs here Configuring Your Bot Using the boilerplate example, to start the bot in production, useīin/hubot -a rocketchat - will install dependencies and run the bot with this Or via the package scripts locally using npm run local or yarn local The bot can then be executed using a bin file in production, as seen here. The Rocket.Chat adapter and Coffeescript for its execution. The boilerplate is essentially just a simple node package that requires Hubot, Note that for bots email, a common workaround to avoid creating multipleĪccounts is to use gmail addresses, e.g. ![]() Use these credentials in the bot's environment ROCKETCHAT_USER and
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |