-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Create process but not start #5768
Comments
You can probably use a config file for it. https://pm2.keymetrics.io/docs/usage/application-declaration/ |
That doesn't work. I opened this issue quite some time ago and never got a response: #5711 |
What is the exact use case of adding an app to the list to launch it later? Why don't you just do |
In our case, we use a CI/CD workflow that ships to production on merge. So we use Ecosystem files with cron schedules defined in the ecosystem file. Therefore, when we merge to production, deployment is automatic, but we do not want all previously defined jobs in our ecosystem to run just because we merged code to production and/or added/deleted a job with it's own cron schedule in the ecosystem file. |
I'm going through the issues to find mentions about not auto-starting a new process, which I now created a PR for: |
Feature landed Update PM2 to 5.4.0 $ npm install [email protected] -g
$ pm2 update |
Let's go! |
Wow! Thanks a lot! |
Is it possible create process and not start it. Save list and then start when you need?
The text was updated successfully, but these errors were encountered: