Merge pull request #163 from krancour/remove-deisctl-refs

doc(*): strike all references to deisctl

Author: krancour

docs/mkdocs.yml

@@ -15,7 +15,6 @@ pages:
     - System Requirements: installing-deis/system-requirements.md
     - Bare Metal: installing-deis/bare-metal.md
     - DigitalOcean: installing-deis/digitalocean.md
-    - Installing deisctl: installing-deis/installing-deisctl.md
     - Installing the Deis Platform: installing-deis/installing-the-deis-platform.md
   - Using Deis:
     - Installing the Client: using-deis/installing-the-client.md

docs/src/contributing/triaging-issues.md

@@ -45,7 +45,6 @@ security     | Security-related issues such as TLS encryption, network segregati
 - client
 - controller
 - database
-- deisctl
 - docs
 - kubernetes
 - registry

docs/src/faq.md

@@ -12,8 +12,4 @@ DAY-iss
 
 Unofficial documentation in Chinese has been created by the DockerOne community.
 
-### What's the difference between the `deis` and `deisctl` clients?
-
-deis is a "dev" tool, used to deploy and scale applications to a Deis Platform. deisctl is an "ops" tool, used to configure and manage the Deis Platform itself.
-
 [dais]: https://en.wikipedia.org/wiki/Dais

docs/src/installing-deis/installing-deisctl.md

@@ -56,7 +56,6 @@ $ kubectl get pods --namespace=deis
 Once you see all of the pods in the `READY` state, your Deis platform is running on a cluster!
 
 
-[install deisctl]: installing-deisctl.md
 [helm]: http://helm.sh
 [using deis]: ../using-deis/deploying-an-application.md
 [configure dns]: ../managing-deis/configuring-dns.md

docs/src/installing-deis/installing-the-deis-platform.md

@@ -22,7 +22,7 @@ defined as:
 
 - the REST API for *deis-controller*
 - etcd keys and values that are publicly documented
-- `deis` and `deisctl` commands and options
+- `deis` commands and options
 - essential `Makefile` targets
 - provider scripts under `contrib/`
 

docs/src/roadmap/release-schedule.md

@@ -32,7 +32,6 @@ Within the scope of this master test plan are these items:
 - The assembled Deis platform on a Kubernetes cluster
 - The HTML documentation set for Deis
 - Binary installers for the `deis` CLI hosted at AWS S3
-- Binary installers for the `deisctl` CLI hosted at AWS S3
 - Hosted HTML documentation updates at http://docs.deis.io/
 - Docker images hosted at <https://registry.hub.docker.com/repos/deis/>
 

docs/src/roadmap/test-plan.md

@@ -7,7 +7,7 @@ grouped into a Control Plane, Data Plane and Router Mesh.
 
 ![Deis System Diagram](DeisSystemDiagram.png)
 
-Operators use the `Deisctl API` to stand up the cluster's Control Plane, Data Plane and Router Mesh.
+Operators use [Helm][] to stand up the cluster's Control Plane, Data Plane and Router Mesh.
 End-users of the platform interact with the Control Plane using the `Deis API`.
 
 The Control Plane dispatches work to the Data Plane via a scheduler.
@@ -65,6 +65,7 @@ See [Isolating the Planes][isolating-planes] for further details.
 [applications]: ../reference-guide/terms.md#application
 [builder]: components.md#builder
 [components]: components.md
+[helm]: http://helm.sh
 [containers]: ../reference-guide/terms.md#container
 [controller]: components.md#controller
 [database]: components.md#database

docs/src/understanding-deis/architecture.md

@@ -8,7 +8,7 @@ To use Deis, you must first register a user on the [Controller][].
 Use `deis register` with the [Controller][] URL (supplied by your Deis administrator)
 to create a new account.  You will be logged in automatically.
 
-The domain you use here should match the one you set with `deisctl config platform set domain=`.
+The domain you use here should match the platform domain you selected when configuring the [Router][].
 Note that you always use `deis.<domain>` to communicate with the controller.
 
     $ deis register http://deis.example.com
@@ -19,13 +19,6 @@ Note that you always use `deis.<domain>` to communicate with the controller.
     Registered myuser
     Logged in as myuser
 
-!!! note
-    For Vagrant clusters: `deis register http://deis.local3.deisapp.com`
-
-!!! note
-    The subdomain can be customized by using `deisctl config controller set subdomain=foo`. The
-    router will then route requests from `foo.<domain>` to the controller.
-
 !!! important
     The first user to register with Deis receives "superuser" privileges. Additional users who
     register will be ordinary users. It's also possible to disable user registration after creating
@@ -73,3 +66,4 @@ If you already have an account, use `deis login` to authenticate against the Dei
 
 
 [controller]: ../understanding-deis/components.md#controller
+[router]: ../understanding-deis/components.md#router