forked from RocketChat/Rocket.Chat
-
Notifications
You must be signed in to change notification settings - Fork 1
Server configuration and Chatbot config requirements
ear-dev edited this page May 21, 2021
·
3 revisions
The versioner takes care of most of the required server configuration versioner: https://git.viasat.com/vega/kluster/blob/master/projects/veranda/rest-api/config_controller.py#L89 config file: https://git.viasat.com/vega/kluster/blob/master/projects/veranda/rest-api/config.json from directory: kluster/projects/veranda
./kluster mongodb -name livechat -namespace default --settings -u shubh -p <PWD> -2fa <TOKEN>
projectID, email, private key, environment=preprod (stored in LastPass)
SF chat endpoint, deploymentID, orgId, buttonID (stored in LastPass)
- I believe we are using the
viasat.notification.service
user for auth when retrieving chat transcript. A personal access token is required for the chatbot fulfillment to retrieve the live chat transcript https://developer.rocket.chat/api/rest-api/personal-access-tokens
generate and communicate to the chatbot team for fulfillment to use
This is technically what happens when a new chat is being instantiated. Just wanted to capture this here for debugging.
- widget loads -> fetch widget config (settings, theme) -> new visitor registered -> new chat created -> agent assigned -> if dialogflow welcome event is sent
-
new chat created
should only happen when the user opens the widget. We have alivechat trigger
configured to control that.