You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When launching a new package follow the standard npm config in package.json. This would allow you to easily pass arguments to the package start script without having to change anything about gardener since you can just edit your package.json.
When using npm start in the forever_bind function the process detaches from forever so gardener can't manage it. Find a way to call npm start from forver without detaching the child process so when gardener stops or restarts the node module processes also die or get restarted.
This patch changes the working dir (CWD) and calls npm start with forever but is insufficient:
When launching a new package follow the standard npm config in package.json. This would allow you to easily pass arguments to the package start script without having to change anything about gardener since you can just edit your package.json.
This function could parse package.json or just call
npm start
. https://github.com/garden20/gardener/blob/master/lib/processes.js#L537The text was updated successfully, but these errors were encountered: