nj-campaign-server v1.1.0

Campaign Server

express stack based campaign server for viber integration

Table Of Contents

• Notes
• Setup and installation
  • Pre-requirements
  • Installation
  • Post installation tests
• Documentation
  • building the documentation
• Scripts
  • start up
  • testing
  • code coverage
  • documentation
  • clean up
• Environment variables
• Miscellanea
  • Dependencies
  • Development dependencies
  • References

Notes

The API documentation is also available in the git hub repo

Setup and installation

Pre-requirements

• git and at least read permission for the repository
• node install v6.8.0 or later
• npm v3.10.8 or later

Installation

$ git clone git@github.com:gitnooji/quiz-express.git

$ npm install

$ cp env.local .env - env file config for localhost or $ cp env.ec2 .env - env file config for ec2 instance.

Post installation tests

The command below is a simple test to make sure the test framework is operational

$ npm run test-mocha

Now run basic unit tests to make sure the product is installed properly

$ npm test

The server needs to be running for the API tests to work.

$ npm start

open a separate terminal and run the api tests as shown below to make sure the server is correctly configured and receiving messages.

$ npm run api-test-local

congratulations you now have a working campaign-server

Documentation

building the documentation

The following scripts will build the documentation

• $ npm run docs (clear and re-create all documentation)
• $ npm run api-docs (create only the api documentation)
• $ npm run coverage-docs (create only the coverage reports)

To view the created documentation run the documentation server as shown below and navigate to the displayed url.

$ npm run doc-server

   Starting up http-server, serving docs
    Available on:
      http://127.0.0.1:8082
      http://10.1.10.111:8082
    Hit CTRL-C to stop the server

Scripts

The following scripts are defined in package.json

start up

• $ npm start start quiz-express
• $ npm run start-dev start inside nodejs-dashboard
• $ npm run start-debug start quiz-express in debug mode with attached devtools. open chrome at the URI provided and enjoy chrome tools debugging

testing

• $ npm test run basic test suite
• $ npm run test-mocha smoke test to make sure mocha is configured
• $ npm run test-auto watch for file changes and rerun tests
• $ npm run test-babel run test suite with .babelrc settings

code coverage

• $ npm run coverage run the code coverage tool. coverage reports are written to the docs folder.

documentation

• $ npm run docs build all the docs.
• $ npm run doc-server start the local documentation server.

clean up

• $ npm clean clean everything and reinstall npm modules
• $ npm run clean-test clean test artifacts
• $ npm run clean-docs clean documentation artifacts
• $ npm run clean-npm remove and re-install npm modules

Environment variables

Environment control vars are defined in the .env file in the root folder of the project. env.local and env.ec2 can be editted and copied to .env

Miscellanea

Dependencies

The production module dependencies can be viewed with the following command

$ npm ls -l -depth=0 --prod

sample output.

quiz-express@1.1.0
│ /home/davey/Code/nooji.io/quiz-express
│ express stack based quiz engine for viber integration
│ git+https://github.com/gitnooji/quiz-express.git
│ https://github.com/gitnooji/quiz-express#readme
├── body-parser@1.15.2
│   Node.js body parsing middleware
│   git+https://github.com/expressjs/body-parser.git
│   https://github.com/expressjs/body-parser#readme
├── chalk@1.1.3
│   Terminal string styling done right. Much color.
│   git+https://github.com/chalk/chalk.git
│   https://github.com/chalk/chalk#readme
├── dotenv@2.0.0
│   Loads environment variables from .env file
│   git://github.com/motdotla/dotenv.git
│   https://github.com/motdotla/dotenv#readme
├── express-api-server@0.0.8
│   An opinionated Express Web API server library
│   git+https://github.com/cgmartin/express-api-server.git
│   https://github.com/cgmartin/express-api-server
└── node-fetch@1.6.3
    A light-weight module that brings window.fetch to node.js and io.js
    git+https://github.com/bitinn/node-fetch.git
    https://github.com/bitinn/node-fetch

Development dependencies

You can view the development dependencies of the project with the following command

$ npm ls -depth=0 --dev

References

• Testing in ES6 with Mocha and Babel 6
• Using Istanbul With Mocha
• Chai Assertion Library
• Markdown quick reference
• Postman/newman
• nodejs-dashboard