add scripts option(custom commands)

[sergeylanzman]

example to use:

1. Go test with custom params or other test framework like ginkgo
2. Fronted tools like grunt
3. Other custom commands(build,deploy etc)

config in Beefile
like command name: command

scripts:
    test: APP_ENV=test APP_CONF_PATH=$(pwd)/conf go test  -v -cover  $(go list ./... | grep -v /vendor/)

This automatic add to commands

know issue not support windows(TODO), not test on linux

Thank for @BorisBorshevsky about idea:)

[astaxie]

the script maybe we can rename it to hook?

[astaxie]

it looks like the makefile's target. I like the idea.

[BorisBorshevsky]

Hi, it seems the same as in package.json (npm), the call it scripts there.

[amrfaissal]

Nice idea, but I don't like the way scripts are added as commands dynamically. I prefer to have an additional run-script command that will load the defined scripts from Beefile and run them by name. For example: $ bee run-script test

[sergeylanzman]

@astaxie @amrfaissal bee run-script XXX is very long. Better way get for user set command as bee command, is very clear and very easy.

[BorisBorshevsky]

seems that this feature is inspired by npm scripts.
maybe it is a good idea to do both.
see npm spec: https://docs.npmjs.com/cli/run-script

npm run-script <command> [-- <args>...]
alias: npm run

@sergeylanzman @amrfaissal

[sergeylanzman]

lets done this issue.
We have nice idea about scripts/hook/custom command.
We have this PR work and #377 (same idea, same implementation, but with color).
@astaxie Your decision what we do with it?

[astaxie]

@sergeylanzman For this PR I think we need to avoid the custom command to overwrite the current command, bee run, bee new etc.

[astaxie]

Just have a conversation with @sergeylanzman in slack. We agree that current implement is good enough to deliver. I think we all agree with this idea.

@amrfaissal I think #377 also can merge into. But I like more short name for it. maybe bee cmd or bee rs

[astaxie]

@amrfaissal I just think about these two solution. support own command and just use the bee run-script command. I think this solution would be more flexible.

[amrfaissal]

@astaxie At least "user-defined" commands should be separated from bee's default commands. Adding commands dynamically is a hack that is both flexible and confusing.
I suggest to create a different slice of commands just for scripts, create a new section called "AVAILABLE SCRIPTS"...etc

[astaxie]

create a new section called "AVAILABLE SCRIPTS"...etc

Yea, that would make more sense. @sergeylanzman Could you help to create another PR to improve it?

[sergeylanzman]

@astaxie yes create this.
We talk about
Beefile settings:

scripts:
    test: ...
    deploy: ...

command for run this bee cmd deploy or bee cmd test
and need create view for this in console maybe with bee cmd print all custom command
Do you want to add something?
I don't know about command in windows, need add in future support windows. Maybe open issue about this.

[astaxie]

Beefile settings:

scripts:
test: ...
deploy: ...
command for run this bee cmd deploy or bee cmd test
and need create view for this in console maybe with bee cmd print all custom command
Do you want to add something?

I agree with this idea. @amrfaissal what's your opinion?

I don't know about command in windows, need add in future support windows. Maybe open issue about this.

I have a window VM. please create a issue for me to track it