This is the Watson Discovery Service Demo
JavaScript CSS Other
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
.bluemix Merge master into release (#88) Jan 17, 2018
config Updates license to MIT Sep 20, 2017
public Update index.html Aug 15, 2018
readme-images Add files via upload Feb 1, 2017
scripts Fix cross-platform scripts (#91) Apr 18, 2018
src Update index.js Aug 15, 2018
test Updates license to MIT Sep 20, 2017
.cfignore initial transfer Feb 1, 2017
.editorconfig initial transfer Feb 1, 2017
.env.enc Support webhose news (#41) Jul 18, 2017
.env.example fix: Add iam_url to constructor Jul 18, 2018
.eslintignore Major refactor (#46) Aug 8, 2017
.eslintrc.json Major refactor (#46) Aug 8, 2017
.gitattributes initial transfer Feb 1, 2017
.gitignore Major refactor (#46) Aug 8, 2017
.releaserc feat: Add semantic releases and IAM support Jul 16, 2018
.travis.yml feat: Add semantic releases and IAM support Jul 16, 2018
.travis_script.sh Update .travis_script.sh May 23, 2017
LICENSE Updates license to MIT Sep 20, 2017
Procfile Major refactor (#46) Aug 8, 2017
README.md docs(README): remove deploy tracker Jul 18, 2018
app.js fix: Add iam_url to constructor Jul 18, 2018
casper-runner.js feat: Add semantic releases and IAM support Jul 16, 2018
deploy.sh Major refactor (#46) Aug 8, 2017
manifest.yml Major refactor (#46) Aug 8, 2017
package-lock.json fix: Add iam_url to constructor Jul 18, 2018
package.json fix: Add iam_url to constructor Jul 18, 2018
repository.yaml Update deployment tracker Dec 18, 2017
server.js fix: Add iam_url to constructor Jul 18, 2018

README.md

🔎 Discovery Demo

Use the IBM Watson Discovery service to add a cognitive search and content analytics engine to your applications to identify patterns, trends and actionable insights that drive better decision-making.

Travis semantic-release

demo

Demo: https://discovery-news-demo.ng.bluemix.net/

Prerequisites

  1. Sign up for an IBM Cloud account.
  2. Download the IBM Cloud CLI.
  3. Create an instance of the Discovery service and get your credentials:
    • Go to the Discovery page in the IBM Cloud Catalog.
    • Log in to your IBM Cloud account.
    • Click Create.
    • Click Show to view the service credentials.
    • Copy the apikey value, or copy the username and password values if your service instance doesn't provide an apikey.
    • Copy the url value.

Configuring the application

  1. In the application folder, copy the .env.example file and create a file called .env

    cp .env.example .env
    
  2. Open the .env file and add the service credentials that you obtained in the previous step.

    Example .env file that configures the apikey and url for a Discovery service instance hosted in the US East region:

    DISCOVERY_IAM_APIKEY=X4rbi8vwZmKpXfowaS3GAsA7vdy17Qh7km5D6EzKLHL2
    DISCOVERY_URL=https://gateway-wdc.watsonplatform.net/discovery/api
    
    • If your service instance uses username and password credentials, add the DISCOVERY_USERNAME and DISCOVERY_PASSWORD variables to the .env file.

    Example .env file that configures the username, password, and url for a Discovery service instance hosted in the Sydney region:

    DISCOVERY_USERNAME=522be-7b41-ab44-dec3-g1eab2ha73c6
    DISCOVERY_PASSWORD=A4Z5BdGENrwu8
    DISCOVERY_URL=https://gateway-syd.watsonplatform.net/discovery/api
    

Running locally

  1. Install the dependencies

    npm install
    
  2. Run the application

    npm start
    
  3. View the application in a browser at localhost:3000

Deploying to IBM Cloud as a Cloud Foundry Application

  1. Login to IBM Cloud with the IBM Cloud CLI

    ibmcloud login
    
  2. Target a Cloud Foundry organization and space.

    ibmcloud target --cf
    
  3. Edit the manifest.yml file. Change the name field to something unique. For example, - name: my-app-name.

  4. Deploy the application

    ibmcloud app push
    
  5. View the application online at the app URL, for example: https://my-app-name.mybluemix.net

Tests

Unit tests

Run unit tests with npm run test-unit, then a to run all tests. See the output for more info.

Integration tests

First you have to make sure your code is built: npm run build

Then run integration tests with: npm run test-integration-runner

Directory structure

.
├── app.js                      // express routes
├── config                      // express configuration
│   ├── error-handler.js
│   ├── express.js
│   └── security.js
├── package.json
├── public                      // static resources
├── server.js                   // entry point
├── test                        // integration tests
└── src                         // react client
    ├── __test__                // unit tests
    └── index.js                // app entry point

License

This sample code is licensed under the MIT License.

Contributing

See CONTRIBUTING.

Open Source @ IBM

Find more open source projects on the IBM Github Page