Skip to content

Commit b6b474b

Browse files
bzp2010SkyeYoung
andauthored
Apply suggestions from @SkyeYoung
Co-authored-by: YYYoung <iskyex@outlook.com>
1 parent c1a597f commit b6b474b

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

docs/en/latest/build-apisix-dev-environment-devcontainers.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -101,10 +101,13 @@ make run
101101
Now you can start writing code and test cases, and testing tools are available:
102102

103103
```shell
104+
export TEST_NGINX_BINARY=openresty
105+
106+
# run all tests
104107
make test
105108

106109
# or run a specify test case file
107-
TEST_NGINX_BINARY=openresty FLUSH_ETCD=1 prove -Itest-nginx/lib -I. -r t/admin/api.t
110+
FLUSH_ETCD=1 prove -Itest-nginx/lib -I. -r t/admin/api.t
108111
```
109112

110113
## FAQ
@@ -113,4 +116,4 @@ TEST_NGINX_BINARY=openresty FLUSH_ETCD=1 prove -Itest-nginx/lib -I. -r t/admin/a
113116

114117
It will be on your host, which is where you cloned the APISIX source code, and the container uses the volume to mount the code into the container. Containers contain only the runtime environment, not the source code, so no changes will be lost whether you close or delete the container.
115118

116-
And, the git is already installed in the container, so you can commit a change directly there.
119+
And, the `git` is already installed in the container, so you can commit a change directly there.

0 commit comments

Comments
 (0)