pm2 pull not working for monorepo
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
What's going wrong?
When dealing with monorepo app, pm2 pull cannot do the intended action.
On one hand, individual workspaces (sub apps) have no git config/repository on their owns, so output is this:
[PM2] No versioning system found for process <app name>
On the other hand, top level repository is not associated with any process, so output is this:
No processes with this name or id : <monorepo name>
How could we reproduce this issue?
- Create monorepo and pull it manually
- Start sub apps as individual processes
- Try to
pm2 pullto update local repository
Supporting information
$ pm2 report
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Reproduce the monorepo setup, start the sub-apps as separate PM2 processes, and run pm2 pull while inspecting the CLI path that resolves repositories and process names. Done means pm2 pull can update the top-level repository for this setup without the reported versioning or process-name errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100