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

Differ between cli and service invokation #51

Closed
vidstige opened this issue Mar 13, 2017 · 4 comments
Closed

Differ between cli and service invokation #51

vidstige opened this issue Mar 13, 2017 · 4 comments

Comments

@vidstige
Copy link
Contributor

I would like to use the command line feature to configure my app like so

$myapp --update --config --file --or --whatever

It could be there is a different script in the package.json that will be run on cli or so.

The main reason is the use case where the user runs the cli without parameters. Here I would like to display program usage as per usual, but there is no way(?) to differ between service starting and starting from cli.

@vidstige
Copy link
Contributor Author

I'm thinking a "cli" key in the "scripts" key in the package.json file. This way we can make it so that if this key is not present, it defaults to what you have now. This way it will not break backwards compatibility.

@vidstige
Copy link
Contributor Author

Another option is to add a way to disable the cli. That way I can plop a different cli in /usr/local/bin/ with the myapp name using the "extra_files" option.

@heartsucker
Copy link
Owner

@vidstige This was fixed in commit 5942570

@vidstige
Copy link
Contributor Author

Ah, this is great 👍

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

No branches or pull requests

2 participants