RanchiMall/node-open-mining-portal
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
Matthew Little 2014-03-13 15:02:50 -06:00
parent 31530e8906
commit 94c643a99f
1 changed files with 38 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

48
README.md
View File

@ -61,19 +61,47 @@ git clone https://github.com/zone117x/node-stratum-portal.git
npm update npm update
``` ```
#### 2) Setup #### 2) Configuration
##### Portal config ##### Portal config
Inside the `config.json` file, ensure the default configuration will work for your environment. The `clustering.forks` Inside the `config.json` file, ensure the default configuration will work for your environment.
option is set to `"auto"` by default which will spawn one process/fork/worker for each CPU core in your system.
Each of these workers will run a separate instance of your pool(s), and the kernel will load balance miners
using these forks. Optionally, the `clustering.forks` field can be a number for how many forks you wish to spawn.
With `blockNotifyListener` enabled, the master process will start listening on the configured port for messages from Explanation for each field:
the `scripts/blockNotify.js` script which your coin daemons can be configured to run when a new block is available. ````javascript
When a blocknotify message is received, the master process uses IPC (inter-process communication) to notify each {
worker process about the message. Each worker process then sends the message to the appropriate coin pool. /* Specifies the level of log output verbosity. Anything more severy than the level specified
See "Setting up blocknotify" below to set up your daemon to use this feature. will also be logged. */
"logLevel": "debug", //or "warning", "error"
/* By default 'forks' is set to "auto" which will spawn one process/fork/worker for each CPU
core in your system. Each of these workers will run a separate instance of your pool(s),
and the kernel will load balance miners using these forks. Optionally, the 'forks' field
can be a number for how many forks will be spawned. */
"clustering": {
"enabled": true,
"forks": "auto"
},
/* With this enabled, the master process will start listening on the configured port for
messages from the 'scripts/blockNotify.js' script which your coin daemons can be configured
to run when a new block is available. When a blocknotify message is received, the master
process uses IPC (inter-process communication) to notify each worker process about the
message. Each worker process then sends the message to the appropriate coin pool. See
"Setting up blocknotify" below to set up your daemon to use this feature. */
"blockNotifyListener": {
"enabled": true,
"port": 8117,
"password": "test"
},
/* This is the front-end. Its not finished. When it is finished, this comment will say so. */
"website": {
"enabled": true,
"port": 80,
"liveStats": true
}
}
````
##### Coin config ##### Coin config