-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
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
Added npm scripts to automate running the workload #71
base: master
Are you sure you want to change the base?
Conversation
@egalli That's great! Please provide some test verification data and issues observed in following scenarios?
|
|
@priyankasprakash Please test these changes to,
|
@egalli I got these two issues when I try to run npm start. @uttampawar This does change the way we run workload when we are running multiple instances. We will have to change the start-server script to incorporate these changes as the start server script has commands to start the mongodb and the server. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@egalli Please address Priyanka's concern before I approve this change.
I can't seem to replicate @priyankasprakash issue, but I explicitly added the dependencies anyways. |
I have added npm scripts to the package.json to start the server, mongodb, runspec, and everything at the same time with default setting. This should increase usability of the workload. All these changes also work in windows.
npm scripts:
npm run server
: starts nodejs serverrpm run mongodb
: creates a "mongodata" folder under the parent and starts mongodb in itrpm run runspec
: starts runspecnpm run start
ornpm start
: all of the above at the same timeNote that this defaults to NODE_ENV=production, if you run in development mode, use
npm run server:dev
ornpm run start:dev