docs(faq): target the published deployment guide

Signed-off-by: XiaoSeS <87064762+XiaoSeS@users.noreply.github.com>
This commit is contained in:
XiaoSeS 2026-09-10 16:15:40 +08:00
parent 41d5f0a3ee
commit c0b2012a9c
4 changed files with 14 additions and 30 deletions

View file

@ -140,7 +140,13 @@ A: When using the OpenClaw CLI, you can specify the namespace using the `<namesp
## Q: What is the recommended deployment method? Can I pull the images and deploy manually?
A: We recommend the official one-line deployment script. Pulling images and deploying manually is not recommended (manual deployment is prone to initialization issues such as being redirected back to the login page after logging in):
A: We recommend the official one-line deployment script. Pulling images and deploying manually is not recommended because it is prone to database initialization, dependency-order, and login redirect issues. By default, dependencies come from public registries, and the SkillHub application images come from GHCR:
```bash
curl -fsSL https://imageless.oss-cn-beijing.aliyuncs.com/runtime.sh | sh -s -- up --public-url https://skillhub.your-company.com
```
If GHCR is unreachable from China, use the Aliyun mirror:
```bash
curl -fsSL https://imageless.oss-cn-beijing.aliyuncs.com/runtime.sh | sh -s -- up --aliyun --public-url https://skillhub.your-company.com --version latest

View file

@ -140,7 +140,13 @@ A: 使用 OpenClaw CLI 命令行工具时,可以通过 `<namespace>--<skill-na
## Q: 推荐的部署方式是什么?可以自己拉镜像手动部署吗?
A: 推荐使用官方一键部署脚本,不建议自己拉取镜像手动部署(手动部署容易出现登录后跳回登录页等初始化问题):
A: 推荐使用官方一键部署脚本,不建议自己拉取镜像手动部署(手动部署容易出现数据库初始化、依赖顺序或登录后跳回登录页等问题)。默认从公共镜像仓库拉取依赖,其中 SkillHub 应用镜像来自 GHCR
```bash
curl -fsSL https://imageless.oss-cn-beijing.aliyuncs.com/runtime.sh | sh -s -- up --public-url https://skillhub.your-company.com
```
国内网络无法访问 GHCR 时,使用阿里云镜像:
```bash
curl -fsSL https://imageless.oss-cn-beijing.aliyuncs.com/runtime.sh | sh -s -- up --aliyun --public-url https://skillhub.your-company.com --version latest

View file

@ -20,20 +20,6 @@ description: 常见问题解答
使用 PostgreSQL 标准备份工具pg_dump
### 国内 / 内网环境部署时镜像拉取失败,或自己拼 compose 启动数据库报错?
优先使用官方的 `runtime.sh` 一键脚本,而不是手写 compose
```bash
# 默认从 ghcr.io 拉取镜像
curl -fsSL https://imageless.oss-cn-beijing.aliyuncs.com/runtime.sh | sh -s -- up --public-url https://skillhub.your-company.com
# 国内网络拉不到 ghcr.io 时,加 --aliyun 走阿里云镜像源
curl -fsSL https://imageless.oss-cn-beijing.aliyuncs.com/runtime.sh | sh -s -- up --aliyun --public-url https://skillhub.your-company.com --version latest
```
脚本会自动准备 PostgreSQL、Redis、对象存储等依赖并按正确顺序启动能避免手写 compose 时常见的数据库初始化 / 依赖顺序报错。完全离线的环境可先用 `scripts/mirror-runtime-images.sh` 把镜像同步到内网 registry再用 `--mirror-registry <地址>` 指向它。
## 使用相关
### 如何重置管理员密码?

View file

@ -20,20 +20,6 @@ Recommended to use reverse proxy (Nginx/Ingress) for TLS termination.
Use PostgreSQL standard backup tools (pg_dump).
### Image pull fails when deploying in China / an intranet, or the database errors when hand-writing compose?
Prefer the official one-line `runtime.sh` script over a hand-written compose file:
```bash
# Pull images from ghcr.io (default)
curl -fsSL https://imageless.oss-cn-beijing.aliyuncs.com/runtime.sh | sh -s -- up --public-url https://skillhub.your-company.com
# If ghcr.io is unreachable in China, add --aliyun to use the Aliyun mirror
curl -fsSL https://imageless.oss-cn-beijing.aliyuncs.com/runtime.sh | sh -s -- up --aliyun --public-url https://skillhub.your-company.com --version latest
```
The script provisions PostgreSQL, Redis and object storage and starts them in the right order, avoiding the database-init / dependency-order errors that commonly appear with a hand-written compose. For fully air-gapped environments, first sync the images to an internal registry with `scripts/mirror-runtime-images.sh`, then point to it with `--mirror-registry <addr>`.
## Usage Related
### How to reset admin password?