This is an automated email from the ASF dual-hosted git repository.
zihaoxiang pushed a commit to branch dev
in repository https://gitbox.apache.org/repos/asf/dolphinscheduler.git
The following commit(s) were added to refs/heads/dev by this push:
new c897b6496a [Doc-18120] Remove irrelevant windows system documents
(#18121)
c897b6496a is described below
commit c897b6496ab673faf993ef92f4df58effa227ed1
Author: xiangzihao <[email protected]>
AuthorDate: Thu Apr 2 09:43:24 2026 +0800
[Doc-18120] Remove irrelevant windows system documents (#18121)
---
docs/docs/en/contribute/join/document.md | 9 ---------
docs/docs/en/contribute/join/review.md | 27 +++++++++++++--------------
docs/docs/en/guide/start/docker.md | 2 --
docs/docs/zh/contribute/join/document.md | 10 ----------
docs/docs/zh/contribute/join/review.md | 27 +++++++++++++--------------
docs/docs/zh/guide/start/docker.md | 3 +--
6 files changed, 27 insertions(+), 51 deletions(-)
diff --git a/docs/docs/en/contribute/join/document.md
b/docs/docs/en/contribute/join/document.md
index 387d31fcfa..83ce18ac96 100644
--- a/docs/docs/en/contribute/join/document.md
+++ b/docs/docs/en/contribute/join/document.md
@@ -20,15 +20,6 @@ git clone
https://github.com/<your-github-user-name>/dolphinscheduler-website
2.2. Run `./scripts/prepare_docs.sh` prepare all related resources, for
more information you could see [how prepare script
work](https://github.com/apache/dolphinscheduler-website/blob/master/HOW_PREPARE_WORK.md)
3. Run `yarn generate` in the root directory to format and prepare the data.
4. Run `yarn dev` in the root directory to start a local server, you will see
the website in 'http://localhost:3000'.
-
-```
-Note: if you clone the code in Windows, not Mac or Linux. Please read the
details below.
-If you execute the commands like the two steps above, you will get the
exception "UnhandledPromiseRejectionWarning: Error: EPERM: operation not
permitted, symlink '2.0.3' -> 'latest'".
-If you get the exception "Can't resolve 'antd' in xxx",you can run `yarn add
antd` and `yarn install`.
-Because the `./scripts/prepare_docs.sh` command requires a Linux environment,
if you are on a Windows system, you can use WSL to complete this step.
-When you encounter this problem. You can run the two steps in cmd.exe as an
administrator on your Windows system.
-```
-
5. Run `yarn build` to build source code, this will automatically generate a
directory called `build`, wait for the execution to complete and into `build`
directory.
6. Verify your change locally: `python -m SimpleHTTPServer 8000`, when your
python version is 3 use :`python3 -m http.server 8000` instead.
diff --git a/docs/docs/en/contribute/join/review.md
b/docs/docs/en/contribute/join/review.md
index 4c1cd36c90..4ae3ff8e25 100644
--- a/docs/docs/en/contribute/join/review.md
+++ b/docs/docs/en/contribute/join/review.md
@@ -36,20 +36,19 @@ Review Issues means discuss [Issues][all-issues] in GitHub
and give suggestions
In addition give suggestion, add label for issue is also important during
review. The labeled issues can be retrieved
better, which convenient for further processing. An issue can with more than
one label. Common issue categories are:
-| Label | Meaning |
-|------------------------------------------|--------------------------------|
-| [UI][label-ui] | UI and front-end related |
-| [security][label-security] | Security Issue |
-| [user experience][label-user-experience] | User experience Issue |
-| [development][label-development] | Development Issue |
-| [Python][label-python] | Python Issue |
-| [plug-in][label-plug-in] | Plug-in Issue |
-| [document][label-document] | Document Issue |
-| [docker][label-docker] | Docker Issue |
-| [need verify][label-need-verify] | Need verify Issue |
-| [e2e][label-e2e] | E2E Issue |
-| [win-os][label-win-os] | windows operating system Issue |
-| [suggestion][label-suggestion] | Give suggestion to us |
+| Label | Meaning |
+|------------------------------------------|--------------------------|
+| [UI][label-ui] | UI and front-end related |
+| [security][label-security] | Security Issue |
+| [user experience][label-user-experience] | User experience Issue |
+| [development][label-development] | Development Issue |
+| [Python][label-python] | Python Issue |
+| [plug-in][label-plug-in] | Plug-in Issue |
+| [document][label-document] | Document Issue |
+| [docker][label-docker] | Docker Issue |
+| [need verify][label-need-verify] | Need verify Issue |
+| [e2e][label-e2e] | E2E Issue |
+| [suggestion][label-suggestion] | Give suggestion to us |
Beside classification, label could also set the priority of Issues. The higher
the priority, the more attention pay
in the community, the easier it is to be fixed or implemented. The priority
label are as follows
diff --git a/docs/docs/en/guide/start/docker.md
b/docs/docs/en/guide/start/docker.md
index f29bcd5c75..9f9745a23a 100644
--- a/docs/docs/en/guide/start/docker.md
+++ b/docs/docs/en/guide/start/docker.md
@@ -46,8 +46,6 @@ $ tar -zxf
apache-dolphinscheduler-"${DOLPHINSCHEDULER_VERSION}"-src.tar.gz
# Going to docker-compose's location
# For Mac or Linux users
$ cd apache-dolphinscheduler-"${DOLPHINSCHEDULER_VERSION}"-src/deploy/docker
-# For Windows users, you should run command `cd
apache-dolphinscheduler-"${DOLPHINSCHEDULER_VERSION}"-src\deploy\docker`
-
# Initialize the database, use profile schema
$ docker-compose --profile schema up -d
diff --git a/docs/docs/zh/contribute/join/document.md
b/docs/docs/zh/contribute/join/document.md
index 13a3214bd0..03205921c1 100644
--- a/docs/docs/zh/contribute/join/document.md
+++ b/docs/docs/zh/contribute/join/document.md
@@ -22,17 +22,7 @@ git clone
https://github.com/<your-github-user-name>/dolphinscheduler-website
- 运行 `./scripts/prepare_docs.sh` 准备所有相关资源
3. 在根目录下运行 `yarn generate` 来格式化和准备数据。
4. 在根目录下运行 `yarn dev` 启动本地服务器，你可以在 http://localhost:3000 查看网站。
-
-```
-注意：如果您在 Windows 而非 Mac 或 Linux 中克隆代码。请阅读下面的详细信息。
-如果执行上述两个步骤中的命令，将出现异常 “UnhandledPromiseRejectionWarning.Error:”： Error： EPERM:
operation not permitted, symlink ‘2.0.3’ -> ‘latest’".
-如果出现异常 “Can't resolve ‘antd’ in xxx”，你可以运行 `yarn add antd` 和 `yarn install`。
-因为这两个步骤运行的命令`./scripts/prepare_docs.sh`应该是 Linux 环境，所以如果你是 Windows 系统，可以使用 WSL
来完成。
-遇到这个问题时。你可以以管理员身份运行 cmd.exe 中的两个步骤。
-```
-
5. 运行 `yarn build` 来构建源代码，此时会自动生成一个名为 `build` 的目录，等待执行完成后进入 `build` 目录。
-
6. 在本地验证你的更改：`python -m SimpleHTTPServer 8000`，当 Python 版本为 3 时，请使用：`python3
-m http.server 8000`。
如果本地安装了更高版本的 Node，可以考虑使用 `nvm` 来允许不同版本的 Node 在你的计算机上运行。
diff --git a/docs/docs/zh/contribute/join/review.md
b/docs/docs/zh/contribute/join/review.md
index bd6d683da3..2a33a43262 100644
--- a/docs/docs/zh/contribute/join/review.md
+++ b/docs/docs/zh/contribute/join/review.md
@@ -31,20 +31,19 @@ Review Issues 是指在 GitHub 中参与 [Issues][all-issues] 的讨论，并在
除了个 issue 建议之外，给 Issue 分类也是非常重要的一个工作。分类后的 Issue 可以更好的被检索，为以后进一步处理提供便利。一个 Issue
可以被打上多个标签，常见的 Issue 分类有
-| 标签 | 标签代表的情况 |
-|------------------------------------------|-----------------------|
-| [UI][label-ui] | UI 以及前端相关的 Issue |
-| [security][label-security] | 安全相关的 Issue |
-| [user experience][label-user-experience] | 用户体验相关的 Issue |
-| [development][label-development] | 开发者相关的 Issue |
-| [Python][label-python] | Python 相关的 Issue |
-| [plug-in][label-plug-in] | 插件相关的 Issue |
-| [document][label-document] | 文档相关的 Issue |
-| [docker][label-docker] | docker 相关的 Issue |
-| [need verify][label-need-verify] | Issue 需要被验证 |
-| [e2e][label-e2e] | e2e 相关的 Issue |
-| [win-os][label-win-os] | windows 操作系统相关的 Issue |
-| [suggestion][label-suggestion] | Issue 为项目提出了建议 |
+| 标签 | 标签代表的情况 |
+|------------------------------------------|------------------|
+| [UI][label-ui] | UI 以及前端相关的 Issue |
+| [security][label-security] | 安全相关的 Issue |
+| [user experience][label-user-experience] | 用户体验相关的 Issue |
+| [development][label-development] | 开发者相关的 Issue |
+| [Python][label-python] | Python 相关的 Issue |
+| [plug-in][label-plug-in] | 插件相关的 Issue |
+| [document][label-document] | 文档相关的 Issue |
+| [docker][label-docker] | docker 相关的 Issue |
+| [need verify][label-need-verify] | Issue 需要被验证 |
+| [e2e][label-e2e] | e2e 相关的 Issue |
+| [suggestion][label-suggestion] | Issue 为项目提出了建议 |
标签除了分类之外，还能区分 Issue 的优先级，优先级越高的标签越重要，越容易被重视，并会尽快被修复或者实现，优先级的标签如下
diff --git a/docs/docs/zh/guide/start/docker.md
b/docs/docs/zh/guide/start/docker.md
index 2a3a577a73..e5fa13ed4c 100644
--- a/docs/docs/zh/guide/start/docker.md
+++ b/docs/docs/zh/guide/start/docker.md
@@ -31,7 +31,7 @@ $ docker run --name dolphinscheduler-standalone-server -p
12345:12345 -p 25333:2
使用 docker-compose 启动服务相比 standalone-server 的优点是 DolphinScheduler
的各个是独立的容器和进程，相互影响降到最小，且能够在
服务重启的时候保留元数据（如需要挂载到本地路径需要做指定）。他更健壮，能保证用户体验更加完整的 DolphinScheduler 服务。这种方式需要先安装
-[docker-compose](https://docs.docker.com/compose/install/)，链接适用于
Mac，Linux，Windows。
+[docker-compose](https://docs.docker.com/compose/install/)，链接适用于 Mac，Linux。
确保 docker-compose 顺利安装后，需要获取 `docker-compose.yaml`
文件，通过[下载页面](https://dolphinscheduler.apache.org/en-us/download/<version>)
下载对应版本源码包可能是最快的方法，当下载完源码后就可以运行命令进行部署了。
@@ -41,7 +41,6 @@ $ DOLPHINSCHEDULER_VERSION=<version>
$ tar -zxf apache-dolphinscheduler-"${DOLPHINSCHEDULER_VERSION}"-src.tar.gz
# Mac Linux 用户
$ cd apache-dolphinscheduler-"${DOLPHINSCHEDULER_VERSION}"-src/deploy/docker
-# Windows 用户, `cd
apache-dolphinscheduler-"${DOLPHINSCHEDULER_VERSION}"-src\deploy\docker`
# 如果需要初始化或者升级数据库结构，需要指定profile为schema
$ docker-compose --profile schema up -d
