summaryrefslogtreecommitdiff
path: root/docs/platform/en.md
diff options
context:
space:
mode:
authorelijah <elijah@riseup.net>2013-02-23 20:49:36 -0800
committerelijah <elijah@riseup.net>2013-02-23 20:49:36 -0800
commit54a9cf79b072be93582e340f73b7562e5ab35b3c (patch)
tree97956362cfd8c90eeda68f3037f578dd4402161f /docs/platform/en.md
parente985329aacbf25b4eeb3e12a57d6a817e9db30be (diff)
added leap_cli command line reference
Diffstat (limited to 'docs/platform/en.md')
-rw-r--r--docs/platform/en.md12
1 files changed, 6 insertions, 6 deletions
diff --git a/docs/platform/en.md b/docs/platform/en.md
index d3dba9b..b029d46 100644
--- a/docs/platform/en.md
+++ b/docs/platform/en.md
@@ -51,7 +51,7 @@ A provider instance directory contains everything needed to manage all the serve
Command line program (leap_cli)
------------------------------------------
-The [command line program](command) `leap` is used by sysadmins to manage everything about a service provider's infrastructure. Except when creating an new provider instance, `leap` is run from within the directory tree of a provider instance.
+The [command line program](commands) `leap` is used by sysadmins to manage everything about a service provider's infrastructure. Except when creating an new provider instance, `leap` is run from within the directory tree of a provider instance.
The `leap` command line has many capabilities, including:
@@ -67,14 +67,14 @@ One other significant difference between LEAP and typical system automation is h
These two approaches, masterless push and pre-compiled static configuration, allow the sysadmin to manage a set of LEAP servers using traditional software development techniques of branching and merging, to more easily create local testing environments using virtual servers, and to deploy without the added complexity and failure potential of a master server.
-The repository for the `leap` command is `git://leap.se/leap_cli`.
+The repository for the `leap` command is `git://leap.se/leap_cli`. It can be installed with `sudo gem install leap_cli`.
Getting started
----------------------------------
We recommend you read the platform documentation in this order:
-1. [quick start tutorial](platform/quick-start).
-2. platform [examples](platform/examples).
-3. the `leap` [command reference](platform/command).
-4. [configuration format](platform/config).
+1. [Quick start tutorial](platform/quick-start).
+2. Platform [examples](platform/examples).
+3. The `leap` [command reference](platform/commands).
+4. [Configuration format](platform/config).