The following document is a step-by-step guide to run BWS.
Ensure MongoDB (2.6+) is installed and running. This document assumes that mongod is running at the default port 27017. See the configuration section to configure a different host/port.
Use the following steps to Install BWS from the npmjs repository and run it with defaults.
npm install bitcore-wallet-service
cd bitcore-wallet-service
To change configuration before running, see the Configuration section.
npm start
Use the following steps to Install BWS from github source and run it with defaults.
git clone https://github.com/bitpay/bitcore-wallet-service.git
cd bitcore-wallet-service
npm install
To change configuration before running, see the Configuration section.
npm start
Configuration for all required modules can be specified in https://github.com/bitpay/bitcore-wallet-service/blob/master/config.js
BWS is composed of 4 separate node services - Message Broker - messagebroker/messagebroker.js Blockchain Monitor - bcmonitor/bcmonitor.js (This service talks to the Blockchain Explorer service configured under blockchainExplorerOpts - see Configure blockchain service below.) Email Service - emailservice/emailservice.js Bitcore Wallet Service - bws.js
Example configuration for connecting to the MongoDB instance:
storageOpts: {
mongoDb: {
uri: 'mongodb://localhost:27017/bws',
},
}
Example configuration for connecting to message broker service:
messageBrokerOpts: {
messageBrokerServer: {
url: 'http://localhost:3380',
},
}
Note: this service will be used by blockchain monitor service as well as by BWS itself. An example of this configuration is:
blockchainExplorerOpts: {
'btc': {
livenet: {
provider: 'v8',
url: 'https://insight.bitpay.com:443',
},
testnet: {
provider: 'v8',
url: 'https://test-insight.bitpay.com:443',
},
},
}
Example configuration for connecting to email service (using postfix):
emailOpts: {
host: 'localhost',
port: 25,
ignoreTLS: true,
subjectPrefix: '[Wallet Service]',
from: '[email protected]',
}
Change config.js
file to enable and configure clustering:
{
cluster: true,
clusterInstances: 4,
}