fix: prioritize pm2.config.js over services in stakgraphSync #2743
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
When both services and pm2.config.js are provided to syncPM2AndServices, pm2.config.js now wins and its content is parsed to update services.
tomsmith8
force-pushed
the
fix/pm2-priority-over-services
branch
from
22a96bd to
fbe4011
Compare
This reverts commit fbe4011.
When pm2.config.js is regenerated from services, now preserves PM2-specific settings (instances, autorestart, watch, max_memory_restart, exec_mode) from the existing pm2.config.js instead of overwriting with hardcoded defaults.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When both services and pm2.config.js are provided to syncPM2AndServices, pm2.config.js now wins and its content is parsed to update services.