Revision abfaa6d9 docs/usage.rst
| b/docs/usage.rst | ||
|---|---|---|
| 1 | 1 |
Usage |
| 2 | 2 |
===== |
| 3 | 3 |
|
| 4 |
Kamaki offers command line interfaces that implement specific command
|
|
| 4 |
Kamaki offers command-line interfaces that implement specific command
|
|
| 5 | 5 |
specifications. A detailed list of the command specifications can be found in |
| 6 | 6 |
`Commands <commands.html>`_ section. This guide covers the generic usage of |
| 7 | 7 |
both interfaces. |
| 8 | 8 |
|
| 9 | 9 |
What's more, kamaki offers a clients API that allows the development of |
| 10 |
external applications for synnefo. The clients API is listed in the
|
|
| 10 |
external applications for Synnefo. The clients API is listed in the
|
|
| 11 | 11 |
`Clients lib <developers/code.html#the-clients-api>`_ section. |
| 12 | 12 |
|
| 13 | 13 |
Quick Setup |
| ... | ... | |
| 33 | 33 |
|
| 34 | 34 |
Shell vs one-command |
| 35 | 35 |
-------------------- |
| 36 |
Kamaki users can access synnefo services through either the interactive shell
|
|
| 36 |
Kamaki users can access Synnefo services through either the interactive shell
|
|
| 37 | 37 |
or the one-command behaviors. In practice, both systems rely on the same |
| 38 | 38 |
command set implementations and API clients, with identical responses and error |
| 39 | 39 |
messages. Still, there are some differences. |
| 40 | 40 |
|
| 41 | 41 |
In favor of interactive shell behavior: |
| 42 | 42 |
|
| 43 |
* tab completion for commands (if supported by host command line shell)
|
|
| 44 |
* session history with ↑ or ↓ keys (if supported by host command line shell)
|
|
| 43 |
* tab completion for commands (if supported by the user's shell)
|
|
| 44 |
* session history with ↑ or ↓ keys (if supported by the user's shell)
|
|
| 45 | 45 |
* shorter commands with command context switching |
| 46 | 46 |
* re-run old commands with /history |
| 47 | 47 |
|
Also available in: Unified diff