How to use configuration files to manage multiple Node.js processes? This article will introduce to you how PM2 uses configuration files to manage multiple Node projects. I hope it will be helpful to you!
1. Introduction to the problem
There are multiple Node.js processes When they need to be managed together, and the parameters required by each are different at the same time, creating a configuration file for management is the best solution.
2. Solution
pm2 init simple
: Can generate a basic version of the configuration file: ecosystem.config.js
// ecosystem.config.js module.exports = { apps: [{ name: "app1", script: "./app.js" }] }
2. Generate a complex version of the configuration file
pm2 init is equivalent to pm2 ecosystem
, you can generate a configuration file with the deploy attribute: economy.config.js
module.exports = { apps: [{ script: 'index.js', watch: '.' }, { script: './service-worker/', watch: ['./service-worker'] }], deploy: { production: { user: 'SSH_USERNAME', host: 'SSH_HOSTMACHINE', ref: 'origin/master', repo: 'GIT_REPOSITORY', path: 'DESTINATION_PATH', 'pre-deploy-local': '', 'post-deploy': 'npm install && pm2 reload ecosystem.config.js --env production', 'pre-setup': '' } } };
This version of the configuration is suitable for remote configuration servers, see the example here!
https://learn-anything.cn/pm2-nodejs-deploy
3. Use the configuration file
to start and stop , restart, reload, delete all projects in the configuration file
pm2 start ecosystem.config.js pm2 stop ecosystem.config.js pm2 restart ecosystem.config.js pm2 reload ecosystem.config.js pm2 delete ecosystem.config.js
Start the specified application
pm2 start ecosystem.config.js --only api-app pm2 start ecosystem.config.js --only "api-app,worker-app"
For more node-related knowledge, please visit: nodejs tutorial! !
The above is the detailed content of How to use configuration files to manage multiple Node.js processes. For more information, please follow other related articles on the PHP Chinese website!