op-guide: move buildFrom to buildPath for docker compose guide

Via: pingcap/docs-cn#893, pingcap/tidb-docker-compose#3
lilin90 · Sep 27, 2018 · 01fe0af · 01fe0af
1 parent 957e85b
commit 01fe0af
Showing 1 changed file with 4 additions and 6 deletions.
diff --git a/op-guide/docker-compose.md b/op-guide/docker-compose.md
@@ -85,8 +85,7 @@ To customize the cluster, you can edit the `docker-compose.yml` file directly. I
 
     ```bash
     cd tidb-docker-compose
-    cp compose/values.yaml values.yaml
-    vim values.yaml
+    vi compose/values.yaml # custom the cluster size, docker image, port mapping and so on
     ```
 
     You can modify the configuration in `values.yaml`, such as the cluster size, TiDB image version, and so on.
@@ -95,14 +94,13 @@ To customize the cluster, you can edit the `docker-compose.yml` file directly. I
 
     For PD, TiKV, TiDB and tidb-vision, you can build Docker images from GitHub source code or local files for development and testing.
 
-    - To build the image of a component from GitHub source code, you need to leave the `image` field empty and set `buildFrom` to `remote`.
-    - To build PD, TiKV or TiDB images from the locally compiled binary file, you need to leave the `image` field empty, set `buildFrom` to `local` and copy the compiled binary file to the corresponding `pd/bin/pd-server`, `tikv/bin/tikv-server`, `tidb/bin/tidb-server`.
-    - To build the tidb-vision image from local, you need to leave the `image` field empty, set `buildFrom` to `local` and copy the tidb-vision project to `tidb-vision/tidb-vision`.
+    - To build PD, TiKV or TiDB images from the locally compiled binary file, you need to leave the `image` field empty and copy the compiled binary file to the corresponding `pd/bin/pd-server`, `tikv/bin/tikv-server`, `tidb/bin/tidb-server`.
+    - To build the tidb-vision image from local, you need to leave the `image` field empty and copy the tidb-vision project to `tidb-vision/tidb-vision`.
 
 4. Generate the `docker-compose.yml` file.
 
     ```bash
-    helm template -f values.yaml compose > generated-docker-compose.yml
+    helm template compose > generated-docker-compose.yaml
     ```
 
 5. Create and start the cluster using the generated `docker-compose.yml` file.