Skip to content

Conversation

@N-McA
Copy link

@N-McA N-McA commented Oct 26, 2016

This is a minor change to allow reusing the same Xvfb screen for multiple processes. Can save resources.

Copy link
Collaborator

@Rob--W Rob--W left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your PR. If you address the following minor comments and squash the changes, then it's ready to be merged,

defaults to `kwallet`.
* `CHROMIUM_EXE_PATH` - Set the path to the Chromium / Google Chrome executable.

* REUSE_XVFB - Default is to start a new Xvfb for each process. Set REUSE_XVFB=true to reuse screen :99 instead.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please keep the line break (add a new line after line 23)

var xvfb = new Xvfb({
silent: true,
// Check environment variable for reuse
reuse:(process.env.REUSE_XVFB === "true"),
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Put a space between reuse: and (.

// Start the virtual X Framebuffer
var xvfb = new Xvfb({
silent: true,
// Check environment variable for reuse
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove this comment, it doesn't add anything that is not already obvious from looking at the code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants