Skip to content

Commit 01cdebe

Browse files
Jiaxin FanJiaxin Fan
authored andcommitted
Checked for typos
1 parent 4af4675 commit 01cdebe

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

tests/src/test/standalone/README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -29,12 +29,12 @@ The following example shows how to generate a Docker image for the Node.js 18 ru
2929
This will return the following runtime image with the name `action-nodejs-v18`, which should be listed after using the `docker images`
3030

3131
## Running the Container
32-
For the purpose of the test. We are going to start the container with a web service running inside it built with Node/Express. In order to access this servicec within the container from the outside, as we are about to do using `curl`, port mapping is done next. By doing so, we access the web service inside docker by first reaching an IP port on `localhost`, which subsequently forwards the request to the docker container's designated port.
33-
In our example, the `Action` container exposes `port 8080` (see the Dockerfile for the associated Docker image), thus we publish the container's `port 8080` to the `localhost` (here, `port 3008` on `localhost` is chosen arbitrarily, as long as the port is not already assigned):
32+
For the purpose of the test. We are going to start the container that has a web service running inside it built using Node/Express. In order to access this service within the container from the outside, as we are about to do using `curl`, port mapping needs to be done next. As a result, we can now access the web service inside docker by first reaching an IP port on `localhost`, which subsequently forwards the request to the docker container's designated port.
33+
In our example, the `Action` container exposes `port 8080` (see the Dockerfile for the associated Docker image), thus we publish the container's `port 8080` to the `localhost` (here, `port 3008` on `localhost` is chosen arbitrarily, as long as the port is not already assigned for something else):
3434
```
3535
docker run --publish 3008:8080 -i -t action-nodejs-v18:latest
3636
```
37-
A simpler way is to map `port 80` on `localhost` to the container's `port 8080`. The port number assigned to the HTTP protocol is `80` Since we will be sending actions against the runtime using HTTP, using this number will allow us to omit the port in the request later. In case `port 80` is already assigned, resort to the method above.
37+
A simpler way is to map `port 80` on `localhost` to the container's `port 8080`. The port number assigned to the HTTP protocol is `80` Since we will be sending actions against the runtime using HTTP, using this number will allow us to omit the port in the request later. Without loss of generality, the following examples will use the arbitrarily chosen `port 3008`
3838

3939
## Testing
4040
This example has prepared a `helloworld.json` file to post using `curl`.

0 commit comments

Comments
 (0)