Update update-pm2.md: suggest backup #249
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi!
Not thinking, I updated PM2 using a remote terminal that runs via PM2. Therefore, when I used
pm2 update
it started to delete all the processes for the update, and once the web server was deleted, the update process stopped and left only 3 of my processes running. I SSHed on and the pm2.dump still had all my old processes - great! Stupidly, I ranpm2 update
again, which wiped them and saved the 3 processes in pm2.dump instead.I don't think it is unreasonable to suggest a backup may be wished before updating. But, perhaps you reckon no one can be that silly when updating, in which case you can leave it out 🤣
Many thanks
Eddie