Unitech / Unitech/pm2

pm2 pull not working if starter-script not in working dir

Open
#3,436 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

S: Open for PR T: Bug
Dominant language
JavaScript
Stars
43.3k
Forks
2.7k
PR merge metrics
No merged PRs in 30d

Description

What's going wrong?

pm2 pull not working if starter-script and executable file not in the same dirs

How to reproduce this issue?

Dirs and files:
/home/start.json
/home/dir/.git
/home/dir/app.py

TestCaseOne:
cat start.json

{
	"name": "app_name",
	"script": "dir/app.py",
	"exec_interpreter": "python3.6"
}

TestCaseTwo:
cat start.json

{
	"name": "app_name",
	"script": "app.py",
	"cwd": "./dir",
	"exec_interpreter": "python3.6"
}

Let's run:
pm2 start start.json
pm2 pull app_name

TestCaseOne: pull successful
TestCaseTwo: there's no .git

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing both pm2 start start.json and pm2 pull app_name cases with the shown /home/start.json, /home/dir/.git, and cwd settings. Compare how pm2 pull resolves the starter script and Git directory; done means the second test case pulls successfully without losing access to .git.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, node.js, python
Domain
cli, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.