User generated content can be store on-premise or in a ServisBOT customer’s private cloud if required due to security or regulation. Our Chat History Server provides secure storage of all conversations with end-users. We provide this through docker containers and images that can be deployed in any infrastructure so that the data and the application is under our customer’s control.
To get access to our CHS images or docker containers, please contact your customer success representative.
The following instructions will walk you through the main pieces required to set up a CHS locally. These steps can be reproduced in your desired cloud or on-prem environment using docker or our instance images.
Contact Customer Support to be provisioned access to our CHS docker
Copy the sample environment file. This can be done by the terminal by running
cp env-sample .env
Adjust the settings to match any alternate requirements that you have.
To initiate the server, just run
docker-compose up -d
This will spin up 2 docker containers. One for the node application, and one for the MySQL server.
You can check the logs for each container to make sure they got spun up properly using a the docker log command.
docker logs sb-remote-conversation-history_mysql-db_1
Once you have the docker container running the main application, you can test the application / database configuration by sending a POST request to the following url.
If you have curl installed, it can be tested with the following command:
curl -I -X POST localhost:8080/ping
ngrok http 8080
If you have purchased this add-on for ServisBOT, reach out to your customer care representative with the URL or domain where your CHS can be reached.
Once everything is configured user generated content will be persisted in your CHS instead of ServisBOT. * Test one of your bots, if you do no have one created yet, follow Getting Started Docs * Review the Chat History * Log into your mysql instance and review the data stored in the messages_v1 table