Skip to content

Commit 32f2f10

Browse files
Merge pull request #11 from AnthonyAmanse/update-readme
Minor README updates
2 parents 4aa59df + 1fc95f2 commit 32f2f10

File tree

2 files changed

+4
-3
lines changed

2 files changed

+4
-3
lines changed

README-Deploy-UI.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
# Deploy through the IBM Cloud Functions console user interface
22

3-
* Create a Trigger
4-
Click on `Create Trigger` then choose `Cloudant`. At the **Cloudant Instance** section, choose to "Input your own credentials". Enter your Cloudant's **Username**, **Password**, **Host**. Enter `images` as your **Database** if you have created that name of the database at the previous step. Name the Trigger "update-trigger".
3+
* Click on `Create Trigger` then choose `Cloudant`. At the **Cloudant Instance** section, choose to "Input your own credentials". Enter your Cloudant's **Username**, **Password**, **Host**. Enter `images` as your **Database** if you have created that name of the database at the previous step. Name the Trigger "update-trigger".
54

65
![create-trigger](docs/create-trigger.png)
76

README.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,9 @@ Choose ["Start Creating"](https://console.bluemix.net/openwhisk/create) in the I
6868

6969
You can also deploy them directly from the CLI by following the steps in the next section.
7070

71-
## Deploy using the wskdeploy command line tool
71+
## Deploy using the `wskdeploy` command line tool
72+
73+
This approach deploy the Cloud Functions with one command driven by the runtime-specific manifest file available in this repository.
7274

7375
Make sure you have the right environment variables in the `local.env` file. Export them in your terminal then deploy the Cloud Functions using `wskdeploy`. This uses the `manifest.yaml` file in this root directory.
7476

0 commit comments

Comments
 (0)