To install single hop, issue the following command:
$ hop install hop_name
You could also use wildcards in names like:
$ hop install hop_*
It will skip all the existing hops.
But if you want to overwrite existing files use --force flag.
$ hop remove hop_*
$ hop serach http*
You define hops in a simple YAML files and placing it in the
~/.hopper/hops directory. See example hops file in ...
Sometimes there's a cases where you want to use project specific
commands that are local to selected workspace. Let's say you are
working on a frontend project than needs the Node.js to build.
You could define node hop for that project only. All you need
is to provide hop.yaml file in your project worksapce directory
and define node hop there. If you call hopper there it will
be started in local mode, which means that it will install all hops
in the local dir instead of user profile and it will use you hop
definitions from local hop.yaml file.
- run local hops from hop.yaml
- run hops with access to host cwd
- run hops using docker API
- run hops on stdin using unix pipes
- use hop stdout with unix pipes
- unit tests
- install hops
- local hops in cwd with hop.yaml
- user hops defined in ~/.hopper/hops/*.yaml
- nice logs output
- hop status command
- uninstall hops
- all hops in cwd
- all user hops
- update hops
- remove dead hops
- add new hops
- hop info command
- installation script
- OSX support
- sexy README
- run hops with host $HOME
-
install --local/user/global - using hopper ENV vars in hops
- support for rkt