Create scripts for all binary commands (generate, generateAction, etc)

[evantahler]

Once we do this, we can update the install instructions to be npm run-script actionHero generate which is a little cleaner

[evantahler]

Might not be possible until this: https://github.com/isaacs/npm/issues/3494
Alternatively, we can suggest to users that they do a global npm install -g install. This is what Sails does.

[evantahler]

work is here, pending we figure out how arg passing will work

https://github.com/evantahler/actionHero/compare/bin_to_script

[NicolasRitouet]

Is there a reason why you don't advise to install actionhero globally ?
That's OS proof, shorter in the tutorials and you need to do it once.
I was surprised to see that when I discovered Actionhero, because all the other frameworks propose that, but maybe you have a good reason :)

[evantahler]

There's nothing wrong from it from an operations POV (IE: it works), but I suggest that new folks keep all packages locally for a few reasons:

• clarity on which version you have
• clarity in which binaries you are running
• ability to inspect source from within project
• clearer debugging when wrappers (cron, deployment tools, forever, etc) can't find binary (usually something to do with ENV or shell)

[jacobfike]

Things like mocha recommend installing globally to get the cli commands, and also installing locally to control the version used by your project. It should be possible to detect what directory the executable is in vs. the current working directory and then call the locally installed actionhero generator, passing it the arguments given to the global one.

That would give you the best of both worlds. All the convenience of system-wide cli commands, but you don't have to worry about version mismatches.

[evantahler]

ahh! That`s a good idea. Please submit a PR!

As a note, I think that the binary global/local passthrough is a good idea, but not really related to this issue.