steelpenny

Steelpenny

nodejs based API for COINS

---

Basic Install

1. Install the package: (global install)

• npm i -g steelpenny

1. Create error log location:

• mkdir /var/log/steelpenny
• Note: must be writeable by the user starting the API

1. Configure your environment according to the REQUIREMENTS.md doc
2. Run the API server:

• /usr/bin/steelpenny
• Make sure your user is the same owner as the logs or has group write permission.

---

Basic Development Install

1. Configure your environment according to the REQUIREMENTS.md doc
2. Verify /var/log/steelpenny directory exists and writable for your development user.
3. Install the dependencies:

$ cd /coins/quarterback/packages/steelpenny
$ npm i

If you are a COINS developer, use: sudo -H -u ansible npm i

1. Run the API:

$ node lib/index.js

Note: Current working directory should be: /coins/quarterback/packages/steelpenny

---

Use node lib/index.js --help to see all available options.

• @flag development/release/production run the server using COINS_ENV of the respective flag. Shorthand --dev/rel/prd are honored.

• @flag without-new-relic start the server without including the New Relic agent. Shorthand -w. Defaults to false.

COINS Internal Usage

• To start the server as a daemon, ansible-provisioned servers should have startup method:

sudo service steelpenny start

• To enable monit monitoring:

sudo monit monitor steelpenny

• Logs are written to the /var/log/steelpenny/ directory on the installed system.

New Relic Integration

The New Relic agent is require()ed on startup by default, however, it does not report to New Relic's servers by default. To turn on reporting, the environment variable NEW_RELIC_ENABLED must be set to 'true'. This should be configured automatically on servers by Ansible: production and staging servers will enable reporting.

When tests are run, the New Relic agent is not require()ed at all. This is accomplished by overriding the cli-options in test/utils/override-cli-opts.js.

Design Specifications

Code

Please refer to CONTRIBUTING.md for details about the code structure, and how to add to it.

Response Format

All responses are a JSON string which parses to an object of the following format:

{
  data: [ ... ],
  error: null | {},
  stats: {will eventually include performance data}
}

It is worth noting that the data property will always be an array, even if only a single value is requested/retrieved.

The error property will be null if no errors have occurred. If an error did occur, then the error object will take the following form:

{
  error: '...',
  message: '...',
  statusCode: ###,
  debugData: {custom debug data}
}

Endpoints

Base URL

All endpoints have a prefix of /api/v#.#.# where v#.#.# is the version in package.json. The one exception to the above rule is GET /api/version, which can be used to retrieve the version via the API itself.

Protocol

By default, this server starts accepting HTTP connections on port 8080. To use HTTPS, place a reverse proxy server in front of this service. production and staging environments should listen for HTTPS connections on port 443, while development systems should listen on port 8443.

Other Endpoints

Please refer to the swagger documentation that is auto-generated by this repo. To view it, start this server npm start, and navigate to the base url + /swagger/documentation (e.g. https://coins-api.mrn.org/swagger/documentation).

Troubleshooting

If things aren't working, go down this quick checklist.

• Is a redis server installed and running locally?

• Have you pulled the latest changes in coins_auth, and run grunt build?

• Is nginx installed, configured and running locally?

• (only if running in COINSTAC mode) Did you create a cloudant account, or mkdir /tmp/coinstac-pouchdb?

If you miss any of these requirements, remove all node modules and reinstall them after installing the requirements.