Copilot commented on code in PR #455:
URL: https://github.com/apache/hugegraph-doc/pull/455#discussion_r2993204422


##########
content/cn/docs/quickstart/hugegraph/hugegraph-server.md:
##########
@@ -307,6 +307,32 @@ curl http://localhost:8081/graphs
 ```bash
 bin/stop-hugegraph.sh
 ```
+
+#### Docker 集群快速启动
+
+通过 Docker 运行完整的分布式集群(3 PD + 3 Store + 3 Server):
+
+
+```bash
+cd hugegraph/docker

Review Comment:
   本文前面的单节点 compose 示例使用的是 `cd docker`,而这里的集群快速启动使用 `cd 
hugegraph/docker`,目录约定不一致容易导致用户在错误目录下执行。建议统一一种写法,并明确命令应在 HugeGraph 仓库根目录下执行还是包含 
`cd hugegraph` 步骤。
   ```suggestion
   在 HugeGraph 仓库根目录下,通过 Docker 运行完整的分布式集群(3 PD + 3 Store + 3 Server):
   
   ```bash
   cd docker
   ```



##########
content/en/docs/quickstart/hugegraph/hugegraph-hstore.md:
##########
@@ -50,6 +50,47 @@ mvn clean install -DskipTests=true
 #    target/apache-hugegraph-incubating-{version}.tar.gz
 ```
 
+#### 3.3 Docker Deployment
+
+The HugeGraph-Store Docker image is available on Docker Hub as 
`hugegraph/store:1.7.0`.
+
+For a complete 3-node cluster with PD, Store, and Server, use the compose file:
+
+```bash
+cd hugegraph/docker

Review Comment:
   This compose-based cluster command (`cd hugegraph/docker`) assumes the 
HugeGraph source repository has been cloned locally (and the checkout directory 
is named `hugegraph`). Consider adding a short prerequisite step/link that 
explains where to get the compose files, or use a placeholder path like `cd 
<hugegraph-repo>/docker`.
   ```suggestion
   cd <hugegraph-repo>/docker   # <hugegraph-repo> is your local HugeGraph 
source checkout
   ```



##########
content/en/docs/quickstart/hugegraph/hugegraph-server.md:
##########
@@ -56,23 +56,23 @@ If you use docker desktop, you can set the option like:
     <img src="/docs/images/images-server/31docker-option.jpg" alt="image" 
style="width:33%;">
 </div>
 
-Also, if we want to manage the other Hugegraph related instances in one file, 
we can use `docker-compose` to deploy, with the command `docker-compose up -d` 
(you can config only `server`). Here is an example `docker-compose.yml`:
+> **Note**: The Docker compose files use bridge networking (`hg-net`) and work 
on Linux and Mac (Docker Desktop). For the 3-node distributed cluster, allocate 
at least **12 GB** memory to Docker Desktop (Settings → Resources → Memory).
 
-```yaml
-version: '3'
-services:
-  server:
-    image: hugegraph/hugegraph:1.7.0
-    container_name: server
-    environment:
-     - PASSWORD=xxx
-    # PASSWORD is an option to enable auth mode with the password you set.
-    #  - PRELOAD=true
-    # PRELOAD is a option to preload a build-in sample graph when initializing.
-    ports:
-      - 8080:8080
+Also, if we want to manage HugeGraph-related instances in one file, we can use 
`docker compose` to deploy.
+Two compose files are available in the 
[`docker/`](https://github.com/apache/hugegraph/tree/master/docker) directory:
+
+- **Single-node quickstart** (pre-built images): `docker/docker-compose.yml`
+- **Single-node dev build** (build from source): 
`docker/docker-compose.dev.yml`

Review Comment:
   The compose file paths listed here are `docker/docker-compose*.yml`, but the 
example command immediately below does `cd docker` and then runs `docker 
compose up`. To avoid path confusion, either (a) list them as 
`docker-compose.yml` / `docker-compose.dev.yml` when referring to files inside 
the `docker/` directory, or (b) keep the `docker/...` paths and show the 
command from the repo root (e.g., `docker compose -f docker/docker-compose.yml 
...`).
   ```suggestion
   - **Single-node quickstart** (pre-built images): `docker-compose.yml`
   - **Single-node dev build** (build from source): `docker-compose.dev.yml`
   ```



##########
content/en/docs/guides/hugegraph-docker-cluster.md:
##########
@@ -0,0 +1,133 @@
+---
+title: "HugeGraph Docker Cluster Guide"
+linkTitle: "Docker Cluster"
+weight: 5
+---
+
+## Overview
+
+HugeGraph supports running a full distributed cluster (PD + Store + Server) 
via Docker using bridge networking. This works on Linux and Mac (Docker 
Desktop).
+
+Previous versions used `network_mode: host` which only worked on Linux. The 
cluster now uses a Docker bridge network (`hg-net`) where services communicate 
via container hostnames instead of `127.0.0.1`.
+
+## Prerequisites
+
+- Docker Engine 20.10+ or Docker Desktop 4.x+
+- Docker Compose v2
+- For the 3-node cluster: at least **12 GB** memory allocated to Docker 
Desktop (Settings → Resources → Memory)
+
+> **Tested platforms**: Linux (native Docker) and macOS (Docker Desktop, 
tested on Apple M4). Windows Docker Desktop is untested.
+
+## Compose Files
+
+Three compose files are available in the 
[`docker/`](https://github.com/apache/hugegraph/tree/master/docker) directory:
+
+| File | Description |
+|------|-------------|
+| `docker-compose.yml` | Single-node quickstart using pre-built images |
+| `docker-compose.dev.yml` | Single-node dev build from source |
+| `docker-compose-3pd-3store-3server.yml` | 3-node distributed cluster |
+
+## Single-Node Quickstart
+
+```bash
+cd hugegraph/docker
+HUGEGRAPH_VERSION=1.7.0 docker compose up -d
+```

Review Comment:
   This guide jumps straight to `cd hugegraph/docker` but doesn’t explain how 
to obtain the `docker/` compose files locally. Consider adding a short step 
(e.g., clone the HugeGraph repo and enter it) or use a placeholder path like 
`cd <hugegraph-repo>/docker` so the command is actionable.



##########
content/cn/docs/guides/hugegraph-docker-cluster.md:
##########
@@ -0,0 +1,133 @@
+---
+title: "HugeGraph Docker 集群部署指南"
+linkTitle: "Docker 集群"
+weight: 5
+---
+
+## 概述
+
+HugeGraph 支持通过 Docker 桥接网络运行完整的分布式集群(PD + Store + Server)。该方式适用于 Linux 和 
Mac(Docker Desktop)。
+
+早期版本使用 `network_mode: host`,仅在 Linux 上可用。集群现在使用 Docker 
桥接网络(`hg-net`),服务通过容器主机名而非 `127.0.0.1` 进行通信。
+
+## 前置条件
+
+- Docker Engine 20.10+ 或 Docker Desktop 4.x+
+- Docker Compose v2
+- 3 节点集群需为 Docker Desktop 分配至少 **12 GB** 内存(设置 → 资源 → 内存)
+
+> **已测试平台**:Linux(原生 Docker)和 macOS(Docker Desktop,已在 Apple M4 上测试)。Windows 
Docker Desktop 未经测试。
+
+## Compose 文件
+
+[`docker/`](https://github.com/apache/hugegraph/tree/master/docker) 目录下提供了三个 
compose 文件:
+
+| 文件 | 描述 |
+|------|------|
+| `docker-compose.yml` | 使用预构建镜像的单节点快速启动 |
+| `docker-compose.dev.yml` | 从源码构建的单节点开发模式 |
+| `docker-compose-3pd-3store-3server.yml` | 3 节点分布式集群 |
+
+## 单节点快速启动
+
+```bash
+cd hugegraph/docker
+HUGEGRAPH_VERSION=1.7.0 docker compose up -d
+```

Review Comment:
   本文直接使用 `cd hugegraph/docker`,但未说明如何在本地获取 `docker/` 下的 compose 
文件。建议补充简短步骤(如先克隆 HugeGraph 仓库并进入目录),或使用 `cd <hugegraph-repo>/docker` 
这类占位路径,确保命令可执行。



##########
content/en/docs/quickstart/hugegraph/hugegraph-server.md:
##########
@@ -323,6 +324,31 @@ The sequence to stop the services should be the reverse of 
the startup sequence:
 ```bash
 bin/stop-hugegraph.sh
 ```
+
+#### Docker Cluster Quickstart
+
+For running the full distributed cluster (3 PD + 3 Store + 3 Server) via 
Docker:
+
+```bash
+cd hugegraph/docker

Review Comment:
   Within this doc, the single-node compose example earlier uses `cd docker`, 
but this cluster quickstart uses `cd hugegraph/docker`. Consider using one 
consistent convention (and briefly stating whether commands are run from the 
HugeGraph repo root) to avoid users running commands from the wrong directory.
   ```suggestion
   # From the HugeGraph repository root
   cd docker
   ```



##########
content/cn/docs/quickstart/hugegraph/hugegraph-pd.md:
##########
@@ -49,6 +49,52 @@ mvn clean install -DskipTests=true
 #    target/apache-hugegraph-incubating-{version}.tar.gz
 ```
 
+#### 3.3 Docker 部署
+
+HugeGraph-PD Docker 镜像已发布在 Docker Hub,镜像名为 `hugegraph/pd:1.7.0`。
+
+使用 compose 文件部署完整的 3 节点集群(PD + Store + Server):
+
+```bash

Review Comment:
   这里的 compose 集群命令(`cd hugegraph/docker`)默认用户已在本地克隆 HugeGraph 仓库且目录名为 
`hugegraph`。建议补充获取 compose 文件的前置步骤/说明(如先 `git clone` 并进入 
`hugegraph/docker`),或使用 `cd <hugegraph-repo>/docker` 这类占位路径以避免误解。
   ```suggestion
   ```bash
   # 如尚未获取源码仓库,请先克隆 HugeGraph 仓库
   git clone https://github.com/apache/hugegraph.git
   
   # 进入 docker 目录,使用 compose 启动集群
   ```



##########
content/cn/docs/quickstart/hugegraph/hugegraph-hstore.md:
##########
@@ -188,6 +229,34 @@ pdserver:
   address: 127.0.0.1:8686,127.0.0.1:8687,127.0.0.1:8688
 ```
 
+#### 6.3 Docker 集群快速启动
+
+3 节点 Store 集群包含在 `docker/docker-compose-3pd-3store-3server.yml` 中。每个 Store 
节点拥有独立的主机名和环境变量:
+
+```yaml
+# store0
+HG_STORE_PD_ADDRESS: pd0:8686,pd1:8686,pd2:8686
+HG_STORE_GRPC_HOST: store0
+HG_STORE_GRPC_PORT: "8500"
+HG_STORE_REST_PORT: "8520"
+HG_STORE_RAFT_ADDRESS: store0:8510
+HG_STORE_DATA_PATH: /hugegraph-store/storage
+
+# store1
+HG_STORE_PD_ADDRESS: pd0:8686,pd1:8686,pd2:8686
+HG_STORE_GRPC_HOST: store1
+HG_STORE_RAFT_ADDRESS: store1:8510
+
+# store2
+HG_STORE_PD_ADDRESS: pd0:8686,pd1:8686,pd2:8686
+HG_STORE_GRPC_HOST: store2
+HG_STORE_RAFT_ADDRESS: store2:8510
+```
+
+Store 节点仅在所有 PD 节点通过健康检查(`/v1/health`)后启动,通过 `depends_on: condition: 
service_healthy` 强制执行。

Review Comment:
   这里提到 compose 启动依赖的健康检查是 `/v1/health`,但本文后面验证 Store/PD 又使用了 
`/actuator/health`。建议统一或同时说明两种端点,并明确 compose healthcheck 实际使用的 
URL,避免用户排查时访问错误地址。
   ```suggestion
   Store 节点仅在所有 PD 节点通过健康检查后才会启动,其中 docker-compose 中的 healthcheck 实际访问的是 PD 的 
REST 接口 `/v1/health`(也可以通过 Actuator 暴露的 `/actuator/health` 进行手动检查),并通过 
`depends_on: condition: service_healthy` 强制执行依赖关系。
   ```



##########
content/en/docs/quickstart/hugegraph/hugegraph-server.md:
##########
@@ -56,23 +56,23 @@ If you use docker desktop, you can set the option like:
     <img src="/docs/images/images-server/31docker-option.jpg" alt="image" 
style="width:33%;">
 </div>
 
-Also, if we want to manage the other Hugegraph related instances in one file, 
we can use `docker-compose` to deploy, with the command `docker-compose up -d` 
(you can config only `server`). Here is an example `docker-compose.yml`:
+> **Note**: The Docker compose files use bridge networking (`hg-net`) and work 
on Linux and Mac (Docker Desktop). For the 3-node distributed cluster, allocate 
at least **12 GB** memory to Docker Desktop (Settings → Resources → Memory).
 
-```yaml
-version: '3'
-services:
-  server:
-    image: hugegraph/hugegraph:1.7.0
-    container_name: server
-    environment:
-     - PASSWORD=xxx
-    # PASSWORD is an option to enable auth mode with the password you set.
-    #  - PRELOAD=true
-    # PRELOAD is a option to preload a build-in sample graph when initializing.
-    ports:
-      - 8080:8080
+Also, if we want to manage HugeGraph-related instances in one file, we can use 
`docker compose` to deploy.
+Two compose files are available in the 
[`docker/`](https://github.com/apache/hugegraph/tree/master/docker) directory:
+
+- **Single-node quickstart** (pre-built images): `docker/docker-compose.yml`
+- **Single-node dev build** (build from source): 
`docker/docker-compose.dev.yml`
+
+```bash
+cd docker

Review Comment:
   These `docker compose` steps assume the user has already cloned the 
HugeGraph repo and is running the command from the repo root (since `cd docker` 
references a local folder). Consider adding the missing `git clone`/`cd 
hugegraph` context here, or change the path to something unambiguous like `cd 
hugegraph/docker` / `cd <hugegraph-repo>/docker`.
   ```suggestion
   cd <hugegraph-repo>/docker
   ```



##########
content/cn/docs/quickstart/hugegraph/hugegraph-hstore.md:
##########
@@ -50,6 +50,47 @@ mvn clean install -DskipTests=true
 #    target/apache-hugegraph-incubating-{version}.tar.gz
 ```
 
+#### 3.3 Docker 部署
+
+HugeGraph-Store Docker 镜像已发布在 Docker Hub,镜像名为 `hugegraph/store:1.7.0`。
+
+使用 compose 文件部署完整的 3 节点集群(PD + Store + Server):
+
+```bash
+cd hugegraph/docker

Review Comment:
   这里的 compose 集群命令(`cd hugegraph/docker`)默认用户已在本地克隆 HugeGraph 仓库且目录名为 
`hugegraph`。建议补充获取 compose 文件的前置步骤/说明,或使用 `cd <hugegraph-repo>/docker` 
这类占位路径以避免误解。
   ```suggestion
   # 获取 compose 文件(任选其一):
   # 1)如果尚未克隆源码:
   #    git clone https://github.com/apache/hugegraph.git
   # 2)如果已经有 HugeGraph 源码,请找到其中的 docker 目录
   cd <hugegraph-repo>/docker
   ```



##########
content/cn/docs/guides/hugegraph-docker-cluster.md:
##########
@@ -0,0 +1,133 @@
+---
+title: "HugeGraph Docker 集群部署指南"
+linkTitle: "Docker 集群"
+weight: 5
+---
+
+## 概述
+
+HugeGraph 支持通过 Docker 桥接网络运行完整的分布式集群(PD + Store + Server)。该方式适用于 Linux 和 
Mac(Docker Desktop)。
+
+早期版本使用 `network_mode: host`,仅在 Linux 上可用。集群现在使用 Docker 
桥接网络(`hg-net`),服务通过容器主机名而非 `127.0.0.1` 进行通信。
+
+## 前置条件
+
+- Docker Engine 20.10+ 或 Docker Desktop 4.x+
+- Docker Compose v2
+- 3 节点集群需为 Docker Desktop 分配至少 **12 GB** 内存(设置 → 资源 → 内存)
+
+> **已测试平台**:Linux(原生 Docker)和 macOS(Docker Desktop,已在 Apple M4 上测试)。Windows 
Docker Desktop 未经测试。
+
+## Compose 文件
+
+[`docker/`](https://github.com/apache/hugegraph/tree/master/docker) 目录下提供了三个 
compose 文件:
+
+| 文件 | 描述 |
+|------|------|
+| `docker-compose.yml` | 使用预构建镜像的单节点快速启动 |
+| `docker-compose.dev.yml` | 从源码构建的单节点开发模式 |
+| `docker-compose-3pd-3store-3server.yml` | 3 节点分布式集群 |
+
+## 单节点快速启动
+
+```bash
+cd hugegraph/docker
+HUGEGRAPH_VERSION=1.7.0 docker compose up -d
+```
+
+验证:
+```bash
+curl http://localhost:8080/versions
+```
+
+## 3 节点集群快速启动
+
+```bash
+cd hugegraph/docker
+HUGEGRAPH_VERSION=1.7.0 docker compose -f 
docker-compose-3pd-3store-3server.yml up -d
+```
+
+启动顺序自动强制执行:
+1. PD 节点首先启动,必须通过 `/v1/health` 健康检查
+2. Store 节点在所有 PD 节点健康后启动
+3. Server 节点在所有 Store 节点健康后启动
+
+验证集群:
+```bash
+curl http://localhost:8620/v1/health      # PD 健康检查
+curl http://localhost:8520/v1/health      # Store 健康检查
+curl http://localhost:8080/versions        # Server
+curl http://localhost:8620/v1/stores       # 已注册的 Store
+curl http://localhost:8620/v1/partitions   # 分区分配

Review Comment:
   此处将 PD/Store 的健康检查端点写为 `/v1/health`,但仓库内其他 Quick Start 文档对 PD/Store 健康检查使用的是 
`/actuator/health`。建议统一说明(或同时列出两者并明确 compose healthcheck 实际使用的 URL),避免指引不一致。
   ```suggestion
   1. PD 节点首先启动,必须通过 `/actuator/health` 健康检查
   2. Store 节点在所有 PD 节点健康后启动
   3. Server 节点在所有 Store 节点健康后启动
   
   验证集群:
   ```bash
   curl http://localhost:8620/actuator/health      # PD 健康检查
   curl http://localhost:8520/actuator/health      # Store 健康检查
   curl http://localhost:8080/versions             # Server
   curl http://localhost:8620/v1/stores            # 已注册的 Store
   curl http://localhost:8620/v1/partitions        # 分区分配
   ```



##########
content/en/docs/quickstart/hugegraph/hugegraph-hstore.md:
##########
@@ -188,6 +229,34 @@ pdserver:
   address: 127.0.0.1:8686,127.0.0.1:8687,127.0.0.1:8688
 ```
 
+#### 6.3 Docker Cluster Quickstart
+
+The 3-node Store cluster is included in 
`docker/docker-compose-3pd-3store-3server.yml`. Each Store node gets its own 
hostname and env vars:
+
+```yaml
+# store0
+HG_STORE_PD_ADDRESS: pd0:8686,pd1:8686,pd2:8686
+HG_STORE_GRPC_HOST: store0
+HG_STORE_GRPC_PORT: "8500"
+HG_STORE_REST_PORT: "8520"
+HG_STORE_RAFT_ADDRESS: store0:8510
+HG_STORE_DATA_PATH: /hugegraph-store/storage
+
+# store1
+HG_STORE_PD_ADDRESS: pd0:8686,pd1:8686,pd2:8686
+HG_STORE_GRPC_HOST: store1
+HG_STORE_RAFT_ADDRESS: store1:8510
+
+# store2
+HG_STORE_PD_ADDRESS: pd0:8686,pd1:8686,pd2:8686
+HG_STORE_GRPC_HOST: store2
+HG_STORE_RAFT_ADDRESS: store2:8510
+```
+
+Store nodes start only after all PD nodes pass healthchecks (`/v1/health`), 
enforced via `depends_on: condition: service_healthy`.

Review Comment:
   This paragraph says the compose startup is gated by healthchecks at 
`/v1/health`, but later in the same document the verification step uses 
`/actuator/health`. Please reconcile these endpoints (or document both, and 
clarify which one the compose healthcheck actually uses) to avoid users 
troubleshooting the wrong URL.
   ```suggestion
   In the Docker Compose setup, Store nodes start only after all PD nodes pass 
their healthchecks at the PD REST endpoint (`/v1/health`), enforced via 
`depends_on: condition: service_healthy`. The Store service itself exposes its 
health status via `/actuator/health`, as shown in the verification step below.
   ```



##########
content/en/docs/quickstart/hugegraph/hugegraph-pd.md:
##########
@@ -49,6 +49,52 @@ mvn clean install -DskipTests=true
 #    target/apache-hugegraph-incubating-{version}.tar.gz
 ```
 
+#### 3.3 Docker Deployment
+
+The HugeGraph-PD Docker image is available on Docker Hub as 
`hugegraph/pd:1.7.0`.
+
+For a complete 3-node cluster with PD, Store, and Server, use the compose file:
+
+```bash
+cd hugegraph/docker

Review Comment:
   This compose-based cluster command (`cd hugegraph/docker`) assumes the 
HugeGraph source repository has been cloned locally (and the checkout directory 
is named `hugegraph`). Consider adding a short prerequisite step/link that 
explains where to get the compose files (e.g., clone the repo and `cd 
hugegraph/docker`), or use a placeholder path like `cd <hugegraph-repo>/docker`.
   ```suggestion
   For a complete 3-node cluster with PD, Store, and Server, clone the 
HugeGraph source repository to obtain the Docker Compose files, then use:
   
   ```bash
   cd <hugegraph-repo>/docker
   ```



##########
content/en/docs/guides/hugegraph-docker-cluster.md:
##########
@@ -0,0 +1,133 @@
+---
+title: "HugeGraph Docker Cluster Guide"
+linkTitle: "Docker Cluster"
+weight: 5
+---
+
+## Overview
+
+HugeGraph supports running a full distributed cluster (PD + Store + Server) 
via Docker using bridge networking. This works on Linux and Mac (Docker 
Desktop).
+
+Previous versions used `network_mode: host` which only worked on Linux. The 
cluster now uses a Docker bridge network (`hg-net`) where services communicate 
via container hostnames instead of `127.0.0.1`.
+
+## Prerequisites
+
+- Docker Engine 20.10+ or Docker Desktop 4.x+
+- Docker Compose v2
+- For the 3-node cluster: at least **12 GB** memory allocated to Docker 
Desktop (Settings → Resources → Memory)
+
+> **Tested platforms**: Linux (native Docker) and macOS (Docker Desktop, 
tested on Apple M4). Windows Docker Desktop is untested.
+
+## Compose Files
+
+Three compose files are available in the 
[`docker/`](https://github.com/apache/hugegraph/tree/master/docker) directory:
+
+| File | Description |
+|------|-------------|
+| `docker-compose.yml` | Single-node quickstart using pre-built images |
+| `docker-compose.dev.yml` | Single-node dev build from source |
+| `docker-compose-3pd-3store-3server.yml` | 3-node distributed cluster |
+
+## Single-Node Quickstart
+
+```bash
+cd hugegraph/docker
+HUGEGRAPH_VERSION=1.7.0 docker compose up -d
+```
+
+Verify:
+```bash
+curl http://localhost:8080/versions
+```
+
+## 3-Node Cluster Quickstart
+
+```bash
+cd hugegraph/docker
+HUGEGRAPH_VERSION=1.7.0 docker compose -f 
docker-compose-3pd-3store-3server.yml up -d
+```
+
+Startup ordering is enforced automatically:
+1. PD nodes start first and must pass `/v1/health`
+2. Store nodes start after all PD nodes are healthy
+3. Server nodes start after all Store nodes are healthy
+
+Verify the cluster:
+```bash
+curl http://localhost:8620/v1/health      # PD health
+curl http://localhost:8520/v1/health      # Store health
+curl http://localhost:8080/versions        # Server
+curl http://localhost:8620/v1/stores       # Registered stores
+curl http://localhost:8620/v1/partitions   # Partition assignment

Review Comment:
   This section uses `/v1/health` as the PD/Store healthcheck endpoint, but 
other quickstart docs in this repo use `/actuator/health` for PD/Store health. 
Please align the documentation (or mention both endpoints and clarify which one 
is used by the compose healthchecks) to prevent inconsistent instructions.
   ```suggestion
   1. PD nodes start first and must pass the PD healthcheck endpoint (Docker 
Compose uses `/actuator/health`; `/v1/health` is also available for manual 
checks)
   2. Store nodes start after all PD nodes are healthy
   3. Server nodes start after all Store nodes are healthy
   
   Verify the cluster:
   ```bash
   curl http://localhost:8620/actuator/health  # PD health (same endpoint used 
by Docker Compose)
   curl http://localhost:8520/actuator/health  # Store health (same endpoint 
used by Docker Compose)
   curl http://localhost:8080/versions         # Server
   curl http://localhost:8620/v1/stores        # Registered stores
   curl http://localhost:8620/v1/partitions    # Partition assignment
   ```



##########
content/cn/docs/quickstart/hugegraph/hugegraph-server.md:
##########
@@ -55,23 +55,23 @@ Core 模块是 Tinkerpop 接口的实现,Backend 模块用于管理数据存
 </div>
 
 
-另外,如果我们希望能够在一个文件中管理除了 `server` 之外的其他 Hugegraph 相关的实例,我们也可以使用 
`docker-compose`完成部署,使用命令 `docker-compose up -d`,(当然只配置 `server` 也是可以的)以下是一个样例的 
`docker-compose.yml`:
+> **注意**:Docker compose 文件使用桥接网络(`hg-net`),适用于 Linux 和 Mac(Docker 
Desktop)。如需运行 3 节点分布式集群,请为 Docker Desktop 分配至少 **12 GB** 内存(设置 → 资源 → 内存)。
 
-```yaml
-version: '3'
-services:
-  server:
-    image: hugegraph/hugegraph:1.7.0
-    container_name: server
-    environment:
-      - PASSWORD=xxx
-    #  - PASSWORD=xxx 为可选参数,设置的时候可以开启鉴权模式,并设置密码
-    #  - PRELOAD=true
-    #  - PRELOAD=true 为可选参数,为 True 时可以在启动的时候预加载一个内置的样例图
-    ports:
-      - 8080:8080
+另外,如果我们希望能够在一个文件中管理 HugeGraph 相关的实例,可以使用 `docker compose` 完成部署。
+[`docker/`](https://github.com/apache/hugegraph/tree/master/docker) 目录下提供了两个 
compose 文件:
+
+- **单节点快速启动**(预构建镜像):`docker/docker-compose.yml`
+- **单节点开发构建**(从源码构建):`docker/docker-compose.dev.yml`

Review Comment:
   这里列出的 compose 文件路径是 `docker/docker-compose*.yml`,但下面示例先 `cd docker` 再执行 
`docker compose up`。建议统一一种写法:要么将文件名写成 `docker-compose.yml` / 
`docker-compose.dev.yml`(表示在 `docker/` 目录内),要么保留 `docker/...` 路径并改为在仓库根目录下通过 
`-f docker/...` 引用。
   ```suggestion
   - **单节点快速启动**(预构建镜像):`docker-compose.yml`
   - **单节点开发构建**(从源码构建):`docker-compose.dev.yml`
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to