This repository is part of the larger Cloud Insurance Co. project.
The admin dashboard provides Cloud Insurance Co. administrators with an overview of the ongoing activities on the site. It starts with real-time view on the chat bot conversations providing admins with insights about the interactions between the chat bot and the visitors. It is possible to delete individual log entries.
This project is designed with several front-end technologies, all on top of a configurable, feature-rich webpack build system that's already setup to provide hot reloading, CSS modules with Sass support, unit testing, code coverage reports, bundle splitting, and a whole lot more, while providing amazing developer tools such as Redux CLI (a generator), Redux devtools (Chrome extension), and Storybook for visually developing and testing components.
In order to deploy the full set of microservices involved, check out the insurance-toolchain repo. Otherwise, you can deploy just the app by following the steps here.
Note that two sample logs are inserted when the app is started. If those two log entries are deleted, they are reinserted on the next start.
- node
^6.7.0 - npm
^3.10.10
-
If you do not already have a IBM Cloud account, sign up here
-
Download and install the IBM Cloud CLI tool
-
The app depends on the main website app. Make sure to deploy it first.
-
Clone the app to your local environment from your terminal using the following command:
git clone https://github.com/IBM-Cloud/insurance-bot-dashboard.git -
cdinto this newly created directory -
Open the
manifest.ymlfile and change thehostvalue to something unique.
The host you choose will determinate the subdomain of your application's URL: <host>.mybluemix.net
-
Connect to IBM Cloud in the command line tool and follow the prompts to log in.
ibmcloud loginUse
ibmcloud target --cfto set org and space; Runibmcloud regionsto find API endpoints. -
Create a Watson Tone Analyzer service.
ibmcloud cf create-service tone_analyzer lite insurance-tone_analyzer -
Build the app web site
npm install npm run deploy:prod -
Push the app to IBM Cloud
ibmcloud cf push --no-start -
Define a variable pointing to the main site deployment.
ibmcloud cf set-env insurance-bot-dashboard SOCKET_URL https://your-insurance-bot.mybluemix.net -
Start your app
ibmcloud cf start insurance-bot-dashboard
And voila! You now have your very own instance of the app running on IBM Cloud.
-
If you do not already have a IBM Cloud account, sign up here
-
The app depends on the main website app. Make sure to deploy it first.
-
Clone the app to your local environment from your terminal using the following command:
git clone https://github.com/IBM-Cloud/insurance-bot-dashboard.git -
cdinto this newly created directory -
Create a new Watson Tone Analyzer service named
insurance-tone_analyzerusing your IBM Cloud account -
Using
vcap-local.template.jsonas template file, createvcap-local.jsoncp vcap-local.template.json vcap-local.jsonReplace the corresponding credentials for the
insurance-tone_analyzerandinsurance-bot-dbservices in yourvcap-local.jsonfile. -
Define an environment variable pointing to the main site (which can be running locally or in IBM Cloud)
export SOCKET_URL=https://localhost:6040 -
Install the required npm packages using the following command
npm install -
Start your app locally with the following command
npm start
This command will start your Node.js web server and print the address where it is listening to requests in the console: server starting on http://localhost:3000.
The Improve component of Watson Assistant provides a history of interactions with users of your application. You can use this history to improve your application's understanding of users' inputs.
- Navigate to IBM Cloud Dashboard and select the Location under which you have created the services.
- Select the
Watson Assistantservice you have created for this app and click Launch tool. - Select
Anaworkspace under Workspaces. - On the Watson Assistant dashboard, click the improve icon on the left pane to see various sections.
Sections of the Improve panel:
- Overview: A summary of conversations that users had with your application.
- User conversations: A list of individual user utterances. You can update intents and entities while viewing an individual user utterance. Note: A single user conversation may consist of multiple utterances.
Webpack is configured to make use of resolve.root, which lets you import local packages as if you were traversing from the root of your ~/src directory. Here's an example:
// current file: ~/src/views/some/nested/View.js
// What used to be this:
import SomeComponent from '../../../components/SomeComponent'
// Can now be this, HORRAY!:
import SomeComponent from 'components/SomeComponent'These are global variables available to you anywhere in your source code. If you wish to modify them, they can be found as the globals key in ~/config/index.js. When adding new globals, make sure you also add them to ~/.eslintrc.
| Variable | Description |
|---|---|
process.env.NODE_ENV |
the active NODE_ENV when the build started |
__DEV__ |
True when process.env.NODE_ENV is development |
__PROD__ |
True when process.env.NODE_ENV is production |
__TEST__ |
True when process.env.NODE_ENV is test |
__DEBUG__ |
True when process.env.NODE_ENV is development and cli arg --no_debug is not set (npm run dev:no-debug) |
__BASENAME__ |
history basename option |
__SOCKET_URL__ |
The websocket endpoint for the main website. It is initialized from process.env.SOCKET_URL variable specified as https://host:port. |
See the Cleanup section in the toolchain repository for instructions on how to remove the resources associated with the entire project.
See License.txt for license information.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent