We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A nice feature would be to allow using this together w/ other popular deployment tools such as capistrano. There is a problem with node-cluster itself with cwd, documented here http://clarkdave.net/2013/02/node-js-and-cluster-cwd-dirname-shenanigans/
A nice feature would be to solve for that here in recluster. Apparently doing this when new workers are spawned would solve the issue.
// http://clarkdave.net/2013/02/node-js-and-cluster-cwd-dirname-shenanigans/ if (__dirname !== process.cwd()) { process.chdir(__dirname); }
Also see #8
The text was updated successfully, but these errors were encountered:
No branches or pull requests
A nice feature would be to allow using this together w/ other popular deployment tools such as capistrano. There is a problem with node-cluster itself with cwd, documented here http://clarkdave.net/2013/02/node-js-and-cluster-cwd-dirname-shenanigans/
A nice feature would be to solve for that here in recluster. Apparently doing this when new workers are spawned would solve the issue.
Also see #8
The text was updated successfully, but these errors were encountered: