Skip to content

Commit

Permalink
Fixing typos
Browse files Browse the repository at this point in the history
  • Loading branch information
Hemankita committed Nov 15, 2017
1 parent d9a3acf commit 84f662e
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 5 deletions.
8 changes: 4 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -526,7 +526,7 @@ fabric-zipkin   1         1         1            1          

Before building the docker image, set the docker environment.

- Run the beow command.
- Run the below command.

`minikube docker-env`

Expand Down Expand Up @@ -607,7 +607,7 @@ In the above case, the access url will be `http://192.168.99.100:31352/WfdDesser

##### [IBM Cloud Private](https://www.ibm.com/cloud-computing/solutions/private-cloud/)

IBM Private Cloud is has all the advantages of public cloud but is dedicated to single organization. You can have your own security requirements and customize the environment as well. Basically it has tight security and gives you more control along with scalability and easy to deploy options. You can run it externally or brhind the firewall of your organization.
IBM Private Cloud is has all the advantages of public cloud but is dedicated to single organization. You can have your own security requirements and customize the environment as well. Basically it has tight security and gives you more control along with scalability and easy to deploy options. You can run it externally or behind the firewall of your organization.

Basically this is an on-premise platform.
1. Includes docker container manager
Expand All @@ -620,7 +620,7 @@ Microservice builder has an option to deploy with IBM Cloud Private. You can set

Microservice Builder runs on a Jenkins pipeline. Basically Jenkins runs in a docker container and it is deployed on Kubernetes using helm.

This jenkins should be integrated with the Github. The repository to which you push the code shold be integrated to Microservice Builder pipeline through Github. Then only Microservice Builder will be able to pick your code.
This jenkins should be integrated with the Github. The repository to which you push the code should be integrated to Microservice Builder pipeline through Github. Then only Microservice Builder will be able to pick your code.

To find instructions on how to set your Microservice Builder pipeline up, click [here](https://www.ibm.com/support/knowledgecenter/en/SS5PWC/pipeline.html).

Expand Down Expand Up @@ -732,4 +732,4 @@ Click on the **http** link there. You will be redirected to the Server page. App
1. [Microservice Builder](https://www.ibm.com/support/knowledgecenter/en/SS5PWC/intro-microservice-builder.html)
2. [Developer Tools CLI](https://console.bluemix.net/docs/cloudnative/dev_cli.html#developercli)
3. [IBM Cloud Private](https://www.ibm.com/support/knowledgecenter/en/SSBS6K_2.1.0/kc_welcome_containers.html)
4. [Micrprofile](https://microprofile.io/)
4. [Microprofile](https://microprofile.io/)
2 changes: 1 addition & 1 deletion usage.txt
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ This project has been enabled to run with IBM cloud developer CLI (https://conso
To make full use of the files generated please note the following:

* Helm charts and Kubernetes deployment files have readiness probes defined that require a health endpoint and port
* Expected port is 9080, default health endpoint is /WfdDessert/rest/dessert
* Expected port is 9080, health endpoint is /WfdDessert/rest/dessert
* Docker support files and IBM cloud deloyment files assume artifact locations based on use of the Liberty Maven plugin (https://github.com/WASdev/ci.maven)
* Expected artifact location is target/WfdDessert-1.0-SNAPSHOT.zip
* Expected Liberty install location is target/liberty/wlp

0 comments on commit 84f662e

Please sign in to comment.