From 63c75b627c3dc5ab97adb7ab6f86fee6bb0bdce6 Mon Sep 17 00:00:00 2001 From: David Liu Date: Tue, 26 Apr 2022 17:29:36 +0800 Subject: [PATCH] Update cc_service.md (#3355) clean up confusing `bin/run` as previous document section Signed-off-by: David Liu --- docs/source/cc_service.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/source/cc_service.md b/docs/source/cc_service.md index 9348c882f23..0f648b24c90 100644 --- a/docs/source/cc_service.md +++ b/docs/source/cc_service.md @@ -27,7 +27,7 @@ code.tar.gz The chaincode package should be used to provide two pieces of information to the external builder and launcher process * identify if the chaincode is an external service. The `bin/detect` section describes an approach using the `metadata.json` file -* provide chaincode endpoint information in a `connection.json` file placed in the release directory. The `bin/run` section describes the `connection.json` file +* provide chaincode endpoint information in a `connection.json` file placed in the release directory. There is plenty of flexibility to gathering the above information. The sample scripts in the [External builder and launcher sample scripts](#external-builder-and-launcher-sample-scripts) illustrate a simple approach to providing the information. As an example of flexibility, consider packaging couchdb index files (see [Add the index to your chaincode folder](couchdb_tutorial.html#add-the-index-to-your-chaincode-folder)). Sample scripts below describe an approach to packaging the files into myccpackage.tar.gz. @@ -64,7 +64,7 @@ externalBuilders: ### External builder and launcher sample scripts -To help understand what each script needs to contain to work with the chaincode as an external service, this section contains samples of `bin/detect` `bin/build`, `bin/release`, and `bin/run` scripts. +To help understand what each script needs to contain to work with the chaincode as an external service, this section contains samples of `bin/detect` `bin/build` and `bin/release` scripts. **Note:** These samples use the `jq` command to parse json. You can run `jq --version` to check if you have it installed. Otherwise, install `jq` or suitably modify the scripts.