Skip to content
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

Add dir column by default on "forever list" #911

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

adelriosantiago
Copy link

This adds the "dir" column by default when issuing the "forever list" command. It is the only field that can help the user to determine which PID is running but it is hidden by default!

I know that it is possible to add an UID, however if the UID is added to the start command in the package.json then it will be commited in GIT, thus not allowing the user to know if is a dev or a prod deployment.

This adds the "dir" column by default when issuing the "forever list". It is the only field that can help the user to determine which PID is currently running but it is hidden by default!

Moreover adding an UID works fine however if the UID is added to the package.json then it will be commited in GIT thus not allowing the user to know if is a dev or a prod deployment.
@adelriosantiago
Copy link
Author

adelriosantiago commented Mar 21, 2017

Example with a common package.json:

  "scripts": {
    "start": "forever --verbose --uid \"node-app\" --watch --watchDirectory ./routes ./bin/www",
    "dev": "nodemon -e ejs,js --debug ./bin/www"
  },

Since package.json is usually commited and the UID can't be set through an ENV variable (or I least I haven't found how) if there are two apps, dev and prod they will both share the same UID.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants