63f8f1fb48
WIP: rewrite of Machine overview for clarity, add diagrams rewrite/re-organize Machine topics; incl. get started on local VM, menu order, titles replaced Swarm info in cloud doc to reference new Swarm provisioning topic per @moxigirl, incorporated review comments per Chanwit into Concepts topic added mention of Swarm clusters to Overview, and links to Swarm topics in What's next for Overview and Concepts updates to concepts per @bfirsh comments updated cloud provisioning topic to illustrated, step-by-step version added for cloud installs per issue #18282 cleanup of links, copy-edits update to concepts, added link to boot2docker repo and re-worded per Nathan's comments updates to concepts and cloud example per @dmp42 comments updated for links and improved intro content for cloud topic Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
65 lines
2.0 KiB
Markdown
65 lines
2.0 KiB
Markdown
<!--[metadata]>
|
|
+++
|
|
title = "Command-line Completion"
|
|
description = "Install Machine command-line completion"
|
|
keywords = ["machine, docker, orchestration, cli, reference"]
|
|
[menu.main]
|
|
identifier="machine_completion"
|
|
parent="workw_machine"
|
|
weight=99
|
|
+++
|
|
<![end-metadata]-->
|
|
|
|
# Command-line Completion
|
|
|
|
Docker Machine comes with [command completion](http://en.wikipedia.org/wiki/Command-line_completion)
|
|
for the bash shell.
|
|
|
|
## Installing Command Completion
|
|
|
|
### Bash
|
|
|
|
Make sure bash completion is installed. If you use a current Linux in a non-minimal installation, bash completion should be available.
|
|
On a Mac, install with `brew install bash-completion`
|
|
|
|
Place the completion scripts in `/etc/bash_completion.d/` (`` `brew --prefix`/etc/bash_completion.d/`` on a Mac), using e.g.
|
|
|
|
files=(docker-machine docker-machine-wrapper docker-machine-prompt)
|
|
for f in "${files[@]}"; do
|
|
curl -L https://raw.githubusercontent.com/docker/machine/v$(docker-machine --version | tr -ds ',' ' ' | awk 'NR==1{print $(3)}')/contrib/completion/bash/$f.bash > `brew --prefix`/etc/bash_completion.d/$f
|
|
done
|
|
|
|
Completion will be available upon next login.
|
|
|
|
<!--
|
|
### Zsh
|
|
|
|
**Note: there does not seem to be any Zsh completion file yet, but when there is, documentation could look like this.**
|
|
|
|
Place the completion scripts in your `/path/to/zsh/completion`, using e.g. `~/.zsh/completion/`
|
|
|
|
mkdir -p ~/.zsh/completion
|
|
files=(docker-machine docker-machine-wrapper docker-machine-prompt)
|
|
for f in "${files[@]}"; do
|
|
curl -L https://raw.githubusercontent.com/docker/machine/v$(docker-machine --version | tr -ds ',' ' ' | awk 'NR==1{print $(3)}')/contrib/completion/zsh/$f > ~/.zsh/completion/_$f
|
|
done
|
|
|
|
Include the directory in your `$fpath`, e.g. by adding in `~/.zshrc`
|
|
|
|
fpath=(~/.zsh/completion $fpath)
|
|
|
|
Make sure `compinit` is loaded or do it by adding in `~/.zshrc`
|
|
|
|
autoload -Uz compinit && compinit -i
|
|
|
|
Then reload your shell
|
|
|
|
exec $SHELL -l
|
|
|
|
-->
|
|
<!--[metadata]>
|
|
## Available completions
|
|
|
|
**TODO**
|
|
<![end-metadata]-->
|