Configurable number of PhantomJS instances from the includer's package.j... #8

Closed
wants to merge 1 commit into
from

Projects

None yet

2 participants

@jakub-g
Collaborator
jakub-g commented Jan 18, 2013

...son

After this commit, one who depends on attester in his "scripts" part of
package.json, can additionally put in that file the following:

 "config":{"phantomjsInstances":2}

to specify the number of PhantomJS instances (instead of passing it via
command line), but as the added benefit, the actual user who npm install'ed
his package, could type:

 npm config set somePackage:phantomjsInstances 8

to take advantage of his multi-core machine.

This setting is taken into account only if there was no
--phantomjs-instances passed from the command line when invoking attester.

@jakub-g jakub-g Configurable number of PhantomJS instances from the includer's packag…
…e.json

After this commit, one who depends on attester in his "scripts" part of
package.json, can additionally put in that file the following:

 "config":{"attesterThreads":2}

to specify the number of PhantomJS instances (instead of passing it via
command line), but as the added benefit, the actual user who npm install'ed
his package, could type:

 npm config set somePackage:attesterThreads 8

to take advantage of his multi-core machine.

This setting is taken into account only if there was no
--phantomjs-instances passed from the command line when invoking attester.
cc6e8e1
@divdavem
Collaborator

Integrated in 12ecafc with the following name for the configuration parameter: phantomjsInstances (instead of attesterThreads)

@divdavem divdavem closed this Jan 22, 2013
@jakub-g jakub-g deleted the jakub-g:cmdLineThreads branch Jan 24, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment