worp1900 / worp

A small CLI utility library I am playing around with to wrap my fingers around go.

worp

A small CLI utility library I am playing around with to wrap my fingers around go.

Install

1. Clone the repository to your go workspace (check your $GOPATH env var where yours is located, mine is ~/workspaces/go. So I would run $ git clone [email protected]:worp1900/worp.git ~/workspaces/go/src/github.com/worp1900/worp ).
2. Then run go install github.com/worp1900/worp to install the binaries.
3. Finally, to see available functionality in worp, run $ worp (without parameters) to see all command available.

Note: Make sure your $GOPATH is in your PATH. This way you'll be able to run the binaries directly, without adding their full path.

Credit where credit is due!

Thanks to http://thenewstack.io/cli-command-line-programming-with-go/ - helped me a lot!

worp's Issues

Externalize the command struct and execute function into an own package

Instead of having an execute functions and a Command struct inside of git.go, they should be externalized to an own package to be used independently.

Add git stash show command

git stash show -p "stash@{<int param>}" should be added to the utility.

Add a PHP section

Features could/should include:
phpunit test execution - configurable on a per project base to tell phpunit where to find it's configuration for running this project's tests?

Enable git module to commit - automatically adding branchname and a commit message

command:
worp commit

result:
git commit -m " "

branchName is the name of the branch the user is currently on. It must be automatically collected.

add git tag to the tool

Running
worp tag <some_tag_name> "<message>"
should resolve in
git tag -a <some_tag_name> -m "<message>"

execute in git module needs to be able to execute and pipe multiple commands...

...instead of receiving parameters and actually treating them as such.

Maybe move the execute to an own module to keep it seperate?

A router is needed to lead through the modules, depending on parameters

Currently everything is solved with if cases and switch statements. This is not flexible.

Error reporting for git package / all packages

The git package currently only reports the failing exit code (1) but should really output which error occured. This should be true for all packages.

Feature Request: OpenSSL interaction

I'd be great to have some of the most often used openssl actions easily available with worp.

A nice set to begin with:
https://www.sslshopper.com/ssl-certificate-tools.html