You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: deploy/hps/README_en.md
+11-11Lines changed: 11 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,9 +11,9 @@ This project provides a high-stability serving solution, consisting of two main
11
11
12
12
**Note: This project relies on the following environment configurations:**
13
13
14
-
-**Operating System**: Linux
15
-
-**Docker Version**: `>= 20.10.0` (Used for image building and deployment)
16
14
-**CPU Architecture**: x86-64
15
+
-**Operating System**: Linux
16
+
-**Docker Engine Version**: `>= 20.10.0` (Used for image building and deployment)
17
17
18
18
This document mainly introduces how to set up a high stability serving environment and package related materials using the scripts provided by this project. The overall process consists of two main stages:
19
19
@@ -32,13 +32,13 @@ Image Building Steps:
32
32
33
33
1. Build a requirement collection image. (Optional)
34
34
2. Freeze requirement versions to improve the reproducibility of deployment image building. (Optional)
35
-
3. Build the deployment image based on the frozen requirement information to generate the final deployment image and provide image support for subsequent pipeline execution.
35
+
3. Build the deployment image based on the frozen requirement information to generate the final deployment image and provide image support for subsequent pipeline execution.
36
36
37
37
**If you do not need to modify requirement-related information, you can skip to [1.3 Building Image](./README_en.md#13-building-image) to build the deployment image using cached requirement information.**
38
38
39
39
## 1.1 Build the Requirement Collection Image (Optional)
40
40
41
-
Navigate to the `server_env` directory and run follow script for building the requirement collection image in this directory.
41
+
Navigate to the `server_env` directory and run follow script for building the requirement collection image in this directory.
42
42
43
43
```bash
44
44
./scripts/prepare_rc_image.sh
@@ -121,10 +121,10 @@ If the basic image cannot be pulled, please refer to the solutions in the [FAQ](
121
121
After run successfully, the command line will display the following message:
=> => naming to ccr-2vdh3abv-pub.cnc.bj.baidubce.com/paddlex/hps:latest-gpu
128
128
```
129
129
130
130
To build both GPU and CPU images run the following command:
@@ -140,7 +140,7 @@ This stage mainly introduces how to package pipeline materials. This function is
140
140
-`client`: Responsible for invoking the model services.
141
141
-`server`: Deployed using the images built in [1. Image Building](./README_en.md#1-image-building), serving as the runtime environment for model services.
142
142
143
-
Before packaging the pipeline materials, you need to switch to the `sdk` directory and run the `scripts/assemble.sh` script in this directory for packaging. For example, to package the general OCR pipeline, run:
143
+
Before packaging the pipeline materials, you need to switch to the `sdk` directory and run the `scripts/assemble.sh` script in this directory for packaging. For example, to package the general OCR pipeline, run:
144
144
145
145
```bash
146
146
./scripts/assemble.sh OCR
@@ -175,7 +175,7 @@ The parameters for the packaging script are described as follows:
175
175
</tbody>
176
176
</table>
177
177
178
-
After run successfully, the packaged will be stored in the `/output` directory.
178
+
After run successfully, the packaged will be stored in the `output` directory.
179
179
180
180
## 3. FAQ
181
181
@@ -191,4 +191,4 @@ When running the image build scripts, you can use the `-p` parameter to specify
0 commit comments