You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by zh...@apache.org on 2022/03/18 11:02:53 UTC
[dolphinscheduler-website] branch master updated: Change structure of the dev directory (#742)
This is an automated email from the ASF dual-hosted git repository.
zhongjiajie pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/dolphinscheduler-website.git
The following commit(s) were added to refs/heads/master by this push:
new 4e0ff48 Change structure of the dev directory (#742)
4e0ff48 is described below
commit 4e0ff48c8fb0bb27d1fdca592aaced0921da11f5
Author: Jiajie Zhong <zh...@hotmail.com>
AuthorDate: Fri Mar 18 19:02:47 2022 +0800
Change structure of the dev directory (#742)
---
docs/en-us/dev/user_doc/about/glossary.md | 79 +++++++++
.../{guide/installation => about}/hardware.md | 0
.../introduction.md} | 0
docs/en-us/dev/user_doc/architecture/design.md | 53 ------
.../dev/user_doc/guide/installation/docker.md | 2 +-
.../dev/user_doc/guide/installation/kubernetes.md | 2 +-
docs/en-us/dev/user_doc/guide/introduction.md | 3 -
.../dev/user_doc/guide/{ => start}/quick-start.md | 0
docs/en-us/release/history-versions.md | 2 +-
docs/zh-cn/dev/user_doc/about/glossary.md | 58 ++++++
.../{guide/installation => about}/hardware.md | 0
.../introduction.md} | 0
docs/zh-cn/dev/user_doc/architecture/design.md | 51 +-----
.../dev/user_doc/guide/installation/kubernetes.md | 2 +-
docs/zh-cn/dev/user_doc/guide/introduction.md | 4 -
.../guide/{installation => start}/docker.md | 2 +-
.../dev/user_doc/guide/{ => start}/quick-start.md | 0
docs/zh-cn/release/history-versions.md | 2 +-
site_config/docsdev.js | 197 ++++++++++++---------
19 files changed, 262 insertions(+), 195 deletions(-)
diff --git a/docs/en-us/dev/user_doc/about/glossary.md b/docs/en-us/dev/user_doc/about/glossary.md
new file mode 100644
index 0000000..541d572
--- /dev/null
+++ b/docs/en-us/dev/user_doc/about/glossary.md
@@ -0,0 +1,79 @@
+## System Architecture Design
+
+Before explaining the architecture of the scheduling system, let's first understand the commonly used terms of the
+scheduling system
+
+### 1.Glossary
+
+**DAG：** The full name is Directed Acyclic Graph, referred to as DAG. Task tasks in the workflow are assembled in the
+form of a directed acyclic graph, and topological traversal is performed from nodes with zero degrees of entry until
+there are no subsequent nodes. Examples are as follows:
+
+<p align="center">
+ <img src="/img/dag_examples_cn.jpg" alt="dag example" width="60%" />
+ <p align="center">
+ <em>dag example</em>
+ </p>
+</p>
+
+**Process definition**: Visualization formed by dragging task nodes and establishing task node associations**DAG**
+
+**Process instance**: The process instance is the instantiation of the process definition, which can be generated by
+manual start or scheduled scheduling. Each time the process definition runs, a process instance is generated
+
+**Task instance**: The task instance is the instantiation of the task node in the process definition, which identifies
+the specific task execution status
+
+**Task type**: Currently supports SHELL, SQL, SUB_PROCESS (sub-process), PROCEDURE, MR, SPARK, PYTHON, DEPENDENT (
+depends), and plans to support dynamic plug-in expansion, note: **SUB_PROCESS** It is also a separate process
+definition that can be started and executed separately
+
+**Scheduling method**: The system supports scheduled scheduling and manual scheduling based on cron expressions. Command
+type support: start workflow, start execution from current node, resume fault-tolerant workflow, resume pause process,
+start execution from failed node, complement, timing, rerun, pause, stop, resume waiting thread. Among them **Resume
+fault-tolerant workflow** and **Resume waiting thread** The two command types are used by the internal control of
+scheduling, and cannot be called from the outside
+
+**Scheduled**: System adopts **quartz** distributed scheduler, and supports the visual generation of cron expressions
+
+**Rely**: The system not only supports **DAG** simple dependencies between the predecessor and successor nodes, but also
+provides **task dependent** nodes, supporting **between processes**
+
+**Priority**: Support the priority of process instances and task instances, if the priority of process instances and
+task instances is not set, the default is first-in-first-out
+
+**Email alert**: Support **SQL task** Query result email sending, process instance running result email alert and fault
+tolerance alert notification
+
+**Failure strategy**: For tasks running in parallel, if a task fails, two failure strategy processing methods are
+provided. **Continue** refers to regardless of the status of the task running in parallel until the end of the process
+failure. **End** means that once a failed task is found, Kill will also run the parallel task at the same time, and the
+process fails and ends
+
+**Complement**: Supplement historical data，Supports **interval parallel and serial** two complement methods
+
+### 2.Module introduction
+
+- dolphinscheduler-alert alarm module, providing AlertServer service.
+
+- dolphinscheduler-api web application module, providing ApiServer service.
+
+- dolphinscheduler-common General constant enumeration, utility class, data structure or base class
+
+- dolphinscheduler-dao provides operations such as database access.
+
+- dolphinscheduler-remote client and server based on netty
+
+- dolphinscheduler-server MasterServer and WorkerServer services
+
+- dolphinscheduler-service service module, including Quartz, Zookeeper, log client access service, easy to call server
+ module and api module
+
+- dolphinscheduler-ui front-end module
+
+### Sum up
+
+From the perspective of scheduling, this article preliminarily introduces the architecture principles and implementation
+ideas of the big data distributed workflow scheduling system-DolphinScheduler. To be continued
+
+
diff --git a/docs/en-us/dev/user_doc/guide/installation/hardware.md b/docs/en-us/dev/user_doc/about/hardware.md
similarity index 100%
rename from docs/en-us/dev/user_doc/guide/installation/hardware.md
rename to docs/en-us/dev/user_doc/about/hardware.md
diff --git a/docs/en-us/dev/user_doc/About_DolphinScheduler/About_DolphinScheduler.md b/docs/en-us/dev/user_doc/about/introduction.md
similarity index 100%
rename from docs/en-us/dev/user_doc/About_DolphinScheduler/About_DolphinScheduler.md
rename to docs/en-us/dev/user_doc/about/introduction.md
diff --git a/docs/en-us/dev/user_doc/architecture/design.md b/docs/en-us/dev/user_doc/architecture/design.md
index 05a1378..d2b8be2 100644
--- a/docs/en-us/dev/user_doc/architecture/design.md
+++ b/docs/en-us/dev/user_doc/architecture/design.md
@@ -1,40 +1,5 @@
# System Architecture Design
-Before explain the architecture of the scheduling system, let's first get to know the terms commonly used in scheduling system.
-
-## Glossary
-
-**DAG：** The full name is Directed Acyclic Graph, the abbreviation is DAG. Tasks in the workflow are assembled in the form of a directed acyclic graph, and topological traversal performs from zero degree entry nodes until there are no subsequent nodes. The following are the examples:
-
-<p align="center">
- <img src="/img/dag_examples_cn.jpg" alt="dag example" width="60%" />
- <p align="center">
- <em>dag example</em>
- </p>
-</p>
-
-**Process definition**: A visualized **DAG** formed by association of task nodes which is created by dragging and dropping.
-
-**Process instance**: The process instance is the instantiation of a process definition, which can be generated by manual start or scheduled scheduling. A process instance generates by everytime process definition runs.
-
-**Task instance**: The task instance is the instantiation of the task node in the process definition, which identifies specific task execution status.
-
-**Task type**: Currently supports shell, SQL, SUB_PROCESS (sub-process), PROCEDURE, MR, SPARK, PYTHON, DEPENDENT (dependent), and plans to support dynamic plug-in extension. Note: **SUB_PROCESS** is also an individual process definition that can be start and execute separately.
-
-**Scheduling method**: The system supports cron expressions based scheduling and manual scheduling. Command type support: start workflow, start execution from current node, resume fault-tolerant workflow, resume pause process, start execution from failed node, complement, timing, rerun, pause, stop, resume waiting thread. Among them **Resume fault-tolerant workflow** and **Resume waiting thread** these command types are controlled by the internal scheduling, and cannot be called from the [...]
-
-**Scheduled**: System adopts **quartz** distributed scheduler, and supports the visual generation of cron expressions.
-
-**Rely**: The system not only supports **DAG** simple dependencies between the predecessor and successor nodes, but also provides **task dependent** nodes, supporting **dependencies between customized tasks of processes**.
-
-**Priority**: Support the priority of process instances and task instances. By default, the priority is first-in-first-out.
-
-**Email alert**: Support send **SQL task** query result email, process instance execution result email alert and fault tolerance alert notification.
-
-**Failure strategy**: For parallel tasks, if a task fails, there are two failure strategy remedy. **Continue** refers to regardless of the status of the task running in parallel until the end of the process failure. **End** means that once a task failed, kill the parallel task, and the process has a failure result and end.
-
-**Complement**: Complement historical data, Supports **interval parallel and serial** two complement methods.
-
## System Structure
### System Architecture Diagram
@@ -311,24 +276,6 @@ public class TaskLogFilter extends Filter<ILoggingEvent> {
}
```
-## Module Introduction
-
-- dolphinscheduler-alert: alarm module, providing AlertServer service.
-
-- dolphinscheduler-api: web application module, providing ApiServer service.
-
-- dolphinscheduler-common: contains general constant enumeration, utility class, data structure and base class.
-
-- dolphinscheduler-dao: provides operations such as database access.
-
-- dolphinscheduler-remote: client and server based on netty.
-
-- dolphinscheduler-server: MasterServer and WorkerServer services.
-
-- dolphinscheduler-service: service module, including Quartz, ZooKeeper, log client access service, convenient for calling from server module and API module.
-
-- dolphinscheduler-ui: front-end module.
-
## Sum Up
From the perspective of scheduling, this article preliminarily introduces the architecture principles and implementation ideas of the big data distributed workflow scheduling system: DolphinScheduler. To be continued.
diff --git a/docs/en-us/dev/user_doc/guide/installation/docker.md b/docs/en-us/dev/user_doc/guide/installation/docker.md
index f581d19..e74d43d 100644
--- a/docs/en-us/dev/user_doc/guide/installation/docker.md
+++ b/docs/en-us/dev/user_doc/guide/installation/docker.md
@@ -60,7 +60,7 @@ The default username is `admin` and the default password is `dolphinscheduler123
<img src="/img/login_en.png" width="60%" />
</p>
-Please refer to the [Quick Start](../quick-start.md) to explore how to use DolphinScheduler.
+Please refer to the [Quick Start](../start/quick-start.md) to explore how to use DolphinScheduler.
### Start via Existing PostgreSQL and ZooKeeper Service
diff --git a/docs/en-us/dev/user_doc/guide/installation/kubernetes.md b/docs/en-us/dev/user_doc/guide/installation/kubernetes.md
index f2769f9..5cd9c1f 100644
--- a/docs/en-us/dev/user_doc/guide/installation/kubernetes.md
+++ b/docs/en-us/dev/user_doc/guide/installation/kubernetes.md
@@ -67,7 +67,7 @@ Access the web: `http://$NODE_IP:$NODE_PORT/dolphinscheduler`.
The default username is `admin` and the default password is `dolphinscheduler123`.
-Please refer to the `Quick Start` in the chapter [Quick Start](../quick-start.md) to explore how to use DolphinScheduler.
+Please refer to the `Quick Start` in the chapter [Quick Start](../start/quick-start.md) to explore how to use DolphinScheduler.
## Uninstall the Chart
diff --git a/docs/en-us/dev/user_doc/guide/introduction.md b/docs/en-us/dev/user_doc/guide/introduction.md
deleted file mode 100644
index 412a326..0000000
--- a/docs/en-us/dev/user_doc/guide/introduction.md
+++ /dev/null
@@ -1,3 +0,0 @@
-# User Manual
-
-The user manual shows common operations about DolphinScheduler. If you still haven't installed DolphinScheduler, refer to the [Quick Start](./quick-start.md) to install DolphinScheduler before going forward.
\ No newline at end of file
diff --git a/docs/en-us/dev/user_doc/guide/quick-start.md b/docs/en-us/dev/user_doc/guide/start/quick-start.md
similarity index 100%
rename from docs/en-us/dev/user_doc/guide/quick-start.md
rename to docs/en-us/dev/user_doc/guide/start/quick-start.md
diff --git a/docs/en-us/release/history-versions.md b/docs/en-us/release/history-versions.md
index 5a67c28..1c3bc70 100644
--- a/docs/en-us/release/history-versions.md
+++ b/docs/en-us/release/history-versions.md
@@ -68,4 +68,4 @@
### Versions：Dev
-#### Links：[Dev Document](../dev/user_doc/guide/quick-start.md)
+#### Links：[Dev Document](../dev/user_doc/about/introduction.md)
diff --git a/docs/zh-cn/dev/user_doc/about/glossary.md b/docs/zh-cn/dev/user_doc/about/glossary.md
new file mode 100644
index 0000000..bcd28ac
--- /dev/null
+++ b/docs/zh-cn/dev/user_doc/about/glossary.md
@@ -0,0 +1,58 @@
+## 名词解释
+
+在对Apache DolphinScheduler了解之前，我们先来认识一下调度系统常用的名词
+
+### 1.名词解释
+
+**DAG：** 全称Directed Acyclic Graph，简称DAG。工作流中的Task任务以有向无环图的形式组装起来，从入度为零的节点进行拓扑遍历，直到无后继节点为止。举例如下图：
+
+<p align="center">
+ <img src="/img/dag_examples_cn.jpg" alt="dag示例" width="60%" />
+ <p align="center">
+ <em>dag示例</em>
+ </p>
+</p>
+
+**流程定义**：通过拖拽任务节点并建立任务节点的关联所形成的可视化**DAG**
+
+**流程实例**：流程实例是流程定义的实例化，可以通过手动启动或定时调度生成,流程定义每运行一次，产生一个流程实例
+
+**任务实例**：任务实例是流程定义中任务节点的实例化，标识着具体的任务执行状态
+
+**任务类型**：目前支持有SHELL、SQL、SUB_PROCESS(子流程)、PROCEDURE、MR、SPARK、PYTHON、DEPENDENT(依赖)、，同时计划支持动态插件扩展，注意：其中子 **SUB_PROCESS**
+也是一个单独的流程定义，是可以单独启动执行的
+
+**调度方式**：系统支持基于cron表达式的定时调度和手动调度。命令类型支持：启动工作流、从当前节点开始执行、恢复被容错的工作流、恢复暂停流程、从失败节点开始执行、补数、定时、重跑、暂停、停止、恢复等待线程。
+其中 **恢复被容错的工作流** 和 **恢复等待线程** 两种命令类型是由调度内部控制使用，外部无法调用
+
+**定时调度**：系统采用 **quartz** 分布式调度器，并同时支持cron表达式可视化的生成
+
+**依赖**：系统不单单支持 **DAG** 简单的前驱和后继节点之间的依赖，同时还提供**任务依赖**节点，支持**流程间的自定义任务依赖**
+
+**优先级** ：支持流程实例和任务实例的优先级，如果流程实例和任务实例的优先级不设置，则默认是先进先出
+
+**邮件告警**：支持 **SQL任务** 查询结果邮件发送，流程实例运行结果邮件告警及容错告警通知
+
+**失败策略**：对于并行运行的任务，如果有任务失败，提供两种失败策略处理方式，**继续**是指不管并行运行任务的状态，直到流程失败结束。**结束**是指一旦发现失败任务，则同时Kill掉正在运行的并行任务，流程失败结束
+
+**补数**：补历史数据，支持**区间并行和串行**两种补数方式
+
+### 2.模块介绍
+
+- dolphinscheduler-alert 告警模块，提供 AlertServer 服务。
+
+- dolphinscheduler-api web应用模块，提供 ApiServer 服务。
+
+- dolphinscheduler-common 通用的常量枚举、工具类、数据结构或者基类
+
+- dolphinscheduler-dao 提供数据库访问等操作。
+
+- dolphinscheduler-remote 基于 netty 的客户端、服务端
+
+- dolphinscheduler-server MasterServer 和 WorkerServer 服务
+
+- dolphinscheduler-service service模块，包含Quartz、Zookeeper、日志客户端访问服务，便于server模块和api模块调用
+
+- dolphinscheduler-ui 前端模块
+
+
diff --git a/docs/zh-cn/dev/user_doc/guide/installation/hardware.md b/docs/zh-cn/dev/user_doc/about/hardware.md
similarity index 100%
rename from docs/zh-cn/dev/user_doc/guide/installation/hardware.md
rename to docs/zh-cn/dev/user_doc/about/hardware.md
diff --git a/docs/zh-cn/dev/user_doc/About_DolphinScheduler/About_DolphinScheduler.md b/docs/zh-cn/dev/user_doc/about/introduction.md
similarity index 100%
rename from docs/zh-cn/dev/user_doc/About_DolphinScheduler/About_DolphinScheduler.md
rename to docs/zh-cn/dev/user_doc/about/introduction.md
diff --git a/docs/zh-cn/dev/user_doc/architecture/design.md b/docs/zh-cn/dev/user_doc/architecture/design.md
index b61ceb8..a2183b0 100644
--- a/docs/zh-cn/dev/user_doc/architecture/design.md
+++ b/docs/zh-cn/dev/user_doc/architecture/design.md
@@ -1,37 +1,4 @@
## 系统架构设计
-在对调度系统架构说明之前，我们先来认识一下调度系统常用的名词
-
-### 1.名词解释
-**DAG：** 全称Directed Acyclic Graph，简称DAG。工作流中的Task任务以有向无环图的形式组装起来，从入度为零的节点进行拓扑遍历，直到无后继节点为止。举例如下图：
-
-<p align="center">
- <img src="/img/dag_examples_cn.jpg" alt="dag示例" width="60%" />
- <p align="center">
- <em>dag示例</em>
- </p>
-</p>
-
-**流程定义**：通过拖拽任务节点并建立任务节点的关联所形成的可视化**DAG**
-
-**流程实例**：流程实例是流程定义的实例化，可以通过手动启动或定时调度生成,流程定义每运行一次，产生一个流程实例
-
-**任务实例**：任务实例是流程定义中任务节点的实例化，标识着具体的任务执行状态
-
-**任务类型**： 目前支持有SHELL、SQL、SUB_PROCESS(子流程)、PROCEDURE、MR、SPARK、PYTHON、DEPENDENT(依赖)、，同时计划支持动态插件扩展，注意：其中子 **SUB_PROCESS** 也是一个单独的流程定义，是可以单独启动执行的
-
-**调度方式：** 系统支持基于cron表达式的定时调度和手动调度。命令类型支持：启动工作流、从当前节点开始执行、恢复被容错的工作流、恢复暂停流程、从失败节点开始执行、补数、定时、重跑、暂停、停止、恢复等待线程。其中 **恢复被容错的工作流** 和 **恢复等待线程** 两种命令类型是由调度内部控制使用，外部无法调用
-
-**定时调度**：系统采用 **quartz** 分布式调度器，并同时支持cron表达式可视化的生成
-
-**依赖**：系统不单单支持 **DAG** 简单的前驱和后继节点之间的依赖，同时还提供**任务依赖**节点，支持**流程间的自定义任务依赖**
-
-**优先级** ：支持流程实例和任务实例的优先级，如果流程实例和任务实例的优先级不设置，则默认是先进先出
-
-**邮件告警**：支持 **SQL任务** 查询结果邮件发送，流程实例运行结果邮件告警及容错告警通知
-
-**失败策略**：对于并行运行的任务，如果有任务失败，提供两种失败策略处理方式，**继续**是指不管并行运行任务的状态，直到流程失败结束。**结束**是指一旦发现失败任务，则同时Kill掉正在运行的并行任务，流程失败结束
-
-**补数**：补历史数据，支持**区间并行和串行**两种补数方式
### 2.系统架构
@@ -97,7 +64,7 @@
* **UI**
- 系统的前端页面，提供系统的各种可视化操作界面，详见[系统使用手册](../guide/introduction.md)部分。
+ 系统的前端页面，提供系统的各种可视化操作界面。
#### 2.3 架构设计思想
@@ -314,22 +281,6 @@ public class TaskLogFilter extends Filter<ILoggingEvent> {
}
```
-### 3.模块介绍
-- dolphinscheduler-alert 告警模块，提供AlertServer服务。
-
-- dolphinscheduler-api web应用模块，提供ApiServer服务。
-
-- dolphinscheduler-common 通用的常量枚举、工具类、数据结构或者基类
-
-- dolphinscheduler-dao 提供数据库访问等操作。
-
-- dolphinscheduler-remote 基于netty的客户端、服务端
-
-- dolphinscheduler-server MasterServer和WorkerServer服务
-
-- dolphinscheduler-service service模块，包含Quartz、Zookeeper、日志客户端访问服务，便于server模块和api模块调用
-
-- dolphinscheduler-ui 前端模块
### 总结
本文从调度出发，初步介绍了大数据分布式工作流调度系统--DolphinScheduler的架构原理及实现思路。未完待续
diff --git a/docs/zh-cn/dev/user_doc/guide/installation/kubernetes.md b/docs/zh-cn/dev/user_doc/guide/installation/kubernetes.md
index 4e17495..e3b0fb5 100644
--- a/docs/zh-cn/dev/user_doc/guide/installation/kubernetes.md
+++ b/docs/zh-cn/dev/user_doc/guide/installation/kubernetes.md
@@ -68,7 +68,7 @@ echo http://$NODE_IP:$NODE_PORT/dolphinscheduler
默认的用户是`admin`，默认的密码是`dolphinscheduler123`
-请参考用户手册章节的[快速上手](../quick-start.md)查看如何使用DolphinScheduler
+请参考用户手册章节的[快速上手](../start/quick-start.md)查看如何使用DolphinScheduler
## 卸载 dolphinscheduler
diff --git a/docs/zh-cn/dev/user_doc/guide/introduction.md b/docs/zh-cn/dev/user_doc/guide/introduction.md
deleted file mode 100644
index 0ba6786..0000000
--- a/docs/zh-cn/dev/user_doc/guide/introduction.md
+++ /dev/null
@@ -1,4 +0,0 @@
-# 系统使用手册
-
-
-用户使用手册向你介绍 DolphinScheduler 所有常见的操作，如果你还没有安装 DolphinScheduler 请参照[快速上手](./quick-start.md) 完成安装
\ No newline at end of file
diff --git a/docs/zh-cn/dev/user_doc/guide/installation/docker.md b/docs/zh-cn/dev/user_doc/guide/start/docker.md
similarity index 99%
rename from docs/zh-cn/dev/user_doc/guide/installation/docker.md
rename to docs/zh-cn/dev/user_doc/guide/start/docker.md
index 86624a2..376944e 100644
--- a/docs/zh-cn/dev/user_doc/guide/installation/docker.md
+++ b/docs/zh-cn/dev/user_doc/guide/start/docker.md
@@ -60,7 +60,7 @@ $ docker-compose up -d
<img src="/img/login.png" width="60%" />
</p>
-请参考用户手册章节的[快速上手](../quick-start.md)查看如何使用DolphinScheduler
+请参考用户手册章节的[快速上手](../start/quick-start.md)查看如何使用DolphinScheduler
### 二、通过指定已存在的 PostgreSQL 和 ZooKeeper 服务
diff --git a/docs/zh-cn/dev/user_doc/guide/quick-start.md b/docs/zh-cn/dev/user_doc/guide/start/quick-start.md
similarity index 100%
rename from docs/zh-cn/dev/user_doc/guide/quick-start.md
rename to docs/zh-cn/dev/user_doc/guide/start/quick-start.md
diff --git a/docs/zh-cn/release/history-versions.md b/docs/zh-cn/release/history-versions.md
index 0d9a7c8..bf2218e 100644
--- a/docs/zh-cn/release/history-versions.md
+++ b/docs/zh-cn/release/history-versions.md
@@ -67,4 +67,4 @@
### 版本：Dev
-#### 地址：[Dev 文档](../dev/user_doc/guide/quick-start.md)
+#### 地址：[Dev 文档](../dev/user_doc/about/introduction.md)
diff --git a/site_config/docsdev.js b/site_config/docsdev.js
index d0f560a..4155faf 100644
--- a/site_config/docsdev.js
+++ b/site_config/docsdev.js
@@ -6,55 +6,56 @@ export default {
children: [
{
title: 'Introduction',
- link: '/en-us/docs/dev/user_doc/About_DolphinScheduler/About_DolphinScheduler.html',
+ link: '/en-us/docs/dev/user_doc/about/introduction.html',
+ },
+ {
+ title: 'Hardware Environment',
+ link: '/en-us/docs/dev/user_doc/about/hardware.html',
+ },
+ {
+ title: 'Glossary',
+ link: '/en-us/docs/dev/user_doc/about/glossary.html',
},
],
},
{
- title: 'User Manual',
+ title: 'Quick Start',
children: [
{
- title: 'Introduction',
- link: '/en-us/docs/dev/user_doc/guide/introduction.html',
+ title: 'Quick Start',
+ link: '/en-us/docs/dev/user_doc/guide/start/quick-start.html',
},
{
- title: 'Quick Start',
- link: '/en-us/docs/dev/user_doc/guide/quick-start.html',
+ title: 'Docker Deployment',
+ link: '/en-us/docs/dev/user_doc/guide/start/docker.html',
},
+ ],
+ },
+ {
+ title: 'Installation',
+ children: [
{
- title: 'Installation',
- children: [
- {
- title: 'Hardware Environment',
- link: '/en-us/docs/dev/user_doc/guide/installation/hardware.html',
- },
- {
- title: 'Standalone Deployment',
- link: '/en-us/docs/dev/user_doc/guide/installation/standalone.html',
- },
- {
- title: 'Pseudo Cluster Deployment',
- link: '/en-us/docs/dev/user_doc/guide/installation/pseudo-cluster.html',
- },
- {
- title: 'Cluster Deployment',
- link: '/en-us/docs/dev/user_doc/guide/installation/cluster.html',
- },
- {
- title: 'Docker Deployment',
- link: '/en-us/docs/dev/user_doc/guide/installation/docker.html',
- },
- {
- title: 'Kubernetes Deployment',
- link: '/en-us/docs/dev/user_doc/guide/installation/kubernetes.html',
- },
- {
- title: 'SkyWalking-Agent Deployment',
- link: '/en-us/docs/dev/user_doc/guide/installation/skywalking-agent.html',
- },
- ],
+ title: 'Standalone Deployment',
+ link: '/en-us/docs/dev/user_doc/guide/installation/standalone.html',
},
{
+ title: 'Pseudo Cluster Deployment',
+ link: '/en-us/docs/dev/user_doc/guide/installation/pseudo-cluster.html',
+ },
+ {
+ title: 'Cluster Deployment',
+ link: '/en-us/docs/dev/user_doc/guide/installation/cluster.html',
+ },
+ {
+ title: 'Kubernetes Deployment',
+ link: '/en-us/docs/dev/user_doc/guide/installation/kubernetes.html',
+ },
+ ],
+ },
+ {
+ title: 'Introduction to Functions',
+ children: [
+ {
title: 'Workflow Overview',
link: '/en-us/docs/dev/user_doc/guide/homepage.html',
},
@@ -250,17 +251,17 @@ export default {
],
},
{
- title: 'Architecture Design',
+ title: 'Architecture Guide',
children: [
{
- title: 'Metadata',
- link: '/en-us/docs/dev/user_doc/architecture/metadata.html',
- },
- {
title: 'Architecture Design',
link: '/en-us/docs/dev/user_doc/architecture/design.html',
},
{
+ title: 'Metadata',
+ link: '/en-us/docs/dev/user_doc/architecture/metadata.html',
+ },
+ {
title: 'Configuration File',
link: '/en-us/docs/dev/user_doc/architecture/configuration.html',
},
@@ -279,6 +280,16 @@ export default {
],
},
{
+ title: 'Observability',
+ children: [
+
+ {
+ title: 'SkyWalking-Agent',
+ link: '/en-us/docs/dev/user_doc/guide/installation/skywalking-agent.html',
+ },
+ ],
+ },
+ {
title: 'FAQ',
children: [
{
@@ -287,6 +298,15 @@ export default {
},
],
},
+ {
+ title: 'Older Versions',
+ children: [
+ {
+ title: 'Older Versions',
+ link: '/en-us/docs/release/history-versions.html',
+ },
+ ],
+ },
],
barText: 'Documentation',
},
@@ -297,55 +317,56 @@ export default {
children: [
{
title: '简介',
- link: '/zh-cn/docs/dev/user_doc/About_DolphinScheduler/About_DolphinScheduler.html',
+ link: '/zh-cn/docs/dev/user_doc/about/introduction.html',
+ },
+ {
+ title: '建议配置',
+ link: '/zh-cn/docs/dev/user_doc/about/hardware.html',
+ },
+ {
+ title: '名词解释',
+ link: '/zh-cn/docs/dev/user_doc/about/glossary.html',
},
],
},
{
- title: '用户手册',
+ title: '快速上手',
children: [
{
- title: '简介',
- link: '/zh-cn/docs/dev/user_doc/guide/introduction.html',
+ title: '快速上手',
+ link: '/zh-cn/docs/dev/user_doc/guide/start/quick-start.html',
},
{
- title: '快速上手',
- link: '/zh-cn/docs/dev/user_doc/guide/quick-start.html',
+ title: 'Docker部署(Docker)',
+ link: '/zh-cn/docs/dev/user_doc/guide/start/docker.html',
},
+ ],
+ },
+ {
+ title: '部署指南',
+ children: [
{
- title: '部署',
- children: [
- {
- title: '软硬件环境建议配置',
- link: '/zh-cn/docs/dev/user_doc/guide/installation/hardware.html',
- },
- {
- title: '单机部署(Standalone)',
- link: '/zh-cn/docs/dev/user_doc/guide/installation/standalone.html',
- },
- {
- title: '伪集群部署(Pseudo-Cluster)',
- link: '/zh-cn/docs/dev/user_doc/guide/installation/pseudo-cluster.html',
- },
- {
- title: '集群部署(Cluster)',
- link: '/zh-cn/docs/dev/user_doc/guide/installation/cluster.html',
- },
- {
- title: 'Docker部署(Docker)',
- link: '/zh-cn/docs/dev/user_doc/guide/installation/docker.html',
- },
- {
- title: 'Kubernetes部署(Kubernetes)',
- link: '/zh-cn/docs/dev/user_doc/guide/installation/kubernetes.html',
- },
- {
- title: 'SkyWalking-Agent部署(SkyWalking)',
- link: '/zh-cn/docs/dev/user_doc/guide/installation/skywalking-agent.html',
- },
- ],
+ title: '单机部署(Standalone)',
+ link: '/zh-cn/docs/dev/user_doc/guide/installation/standalone.html',
},
{
+ title: '伪集群部署(Pseudo-Cluster)',
+ link: '/zh-cn/docs/dev/user_doc/guide/installation/pseudo-cluster.html',
+ },
+ {
+ title: '集群部署(Cluster)',
+ link: '/zh-cn/docs/dev/user_doc/guide/installation/cluster.html',
+ },
+ {
+ title: 'Kubernetes部署(Kubernetes)',
+ link: '/zh-cn/docs/dev/user_doc/guide/installation/kubernetes.html',
+ },
+ ],
+ },
+ {
+ title: '功能介绍',
+ children: [
+ {
title: '指标总览',
link: '/zh-cn/docs/dev/user_doc/guide/homepage.html',
},
@@ -570,6 +591,15 @@ export default {
],
},
{
+ title: '可观测性',
+ children: [
+ {
+ title: 'SkyWalking-Agent',
+ link: '/zh-cn/docs/dev/user_doc/guide/installation/skywalking-agent.html',
+ },
+ ],
+ },
+ {
title: 'FAQ',
children: [
{
@@ -578,6 +608,15 @@ export default {
},
],
},
+ {
+ title: '历史版本',
+ children: [
+ {
+ title: '历史版本',
+ link: '/zh-cn/docs/release/history-versions.html',
+ },
+ ],
+ },
],
barText: '文档',
},