mirror of
https://gitee.com/dolphinscheduler/DolphinScheduler.git
synced 2024-11-29 18:58:05 +08:00
[Doc] Add tools/libs to the init database steps (#11345)
This commit is contained in:
xiangzihao
GitHub
parent
3061bbc5c4
commit
983f9b41bf
@ -96,13 +96,9 @@ You are very welcome to communicate with the developers and users of Dolphin Sch
|
||||
1. Join the Slack channel [Slack](https://asf-dolphinscheduler.slack.com/).
|
||||
2. Follow the [Twitter account of DolphinScheduler](https://twitter.com/dolphinschedule) and get the latest news on time.
|
||||
|
||||
### Contributor over time
|
||||
|
||||
[](https://www.apiseven.com/en/contributor-graph?chart=contributorOverTime&repo=apache/dolphinscheduler)
|
||||
|
||||
## How to Contribute
|
||||
|
||||
The community welcomes everyone to contribute, please refer to this page to find out more: [How to contribute](https://dolphinscheduler.apache.org/en-us/community/development/contribute.html).
|
||||
The community welcomes everyone to contribute, please refer to this page to find out more: [How to contribute](docs/docs/en/contribute/join/contribute.md).
|
||||
|
||||
# Landscapes
|
||||
|
||||
|
||||
@ -48,7 +48,7 @@ DolphinScheduler的工作计划：<a href="https://github.com/apache/dolphinsche
|
||||
## 参与贡献
|
||||
|
||||
非常欢迎大家来参与贡献，贡献流程请参考：
|
||||
[[参与贡献](https://dolphinscheduler.apache.org/zh-cn/community/development/contribute.html)]
|
||||
[[参与贡献](docs/docs/zh/contribute/join/contribute.md)]
|
||||
|
||||
## 快速试用 Docker
|
||||
|
||||
|
||||
@ -87,7 +87,7 @@ https://github.com/apache/dolphinscheduler/tree/dev/dolphinscheduler-api-test/do
|
||||
## Supplements
|
||||
|
||||
When running API tests locally, First, you need to start the local service, you can refer to this page:
|
||||
[development-environment-setup](https://dolphinscheduler.apache.org/en-us/development/development-environment-setup.html)
|
||||
[development-environment-setup](./development-environment-setup.md)
|
||||
|
||||
When running API tests locally, the `-Dlocal=true` parameter can be configured to connect locally and facilitate changes to the UI.
|
||||
|
||||
|
||||
@ -179,7 +179,7 @@ https://github.com/apache/dolphinscheduler/tree/dev/dolphinscheduler-e2e/dolphin
|
||||
## III. Supplements
|
||||
|
||||
When running E2E tests locally, First, you need to start the local service, you can refer to this page:
|
||||
[development-environment-setup](https://dolphinscheduler.apache.org/en-us/development/development-environment-setup.html)
|
||||
[development-environment-setup](./development-environment-setup.md)
|
||||
|
||||
When running E2E tests locally, the `-Dlocal=true` parameter can be configured to connect locally and facilitate changes to the UI.
|
||||
|
||||
|
||||
@ -29,7 +29,7 @@ In each issue, we list the content to be tested and the expected results, which
|
||||
|
||||
### How to write test code?
|
||||
|
||||
After taking up the corresponding task, the next step is to get to the crux of writing the code. Many partners may not be familiar with E2E test codes, so you can refer to this page: [e2e-test](https://dolphinscheduler.apache.org/en-us/development/e2e-test.html).
|
||||
After taking up the corresponding task, the next step is to get to the crux of writing the code. Many partners may not be familiar with E2E test codes, so you can refer to this page: [e2e-test](../e2e-test.md).
|
||||
|
||||
### How to submit a Pull Request?
|
||||
|
||||
|
||||
@ -20,7 +20,7 @@ export SPRING_DATASOURCE_PASSWORD={password}
|
||||
## Pseudo-Cluster/Cluster Initialize the Database
|
||||
|
||||
DolphinScheduler metadata is stored in the relational database. Currently, supports PostgreSQL and MySQL. If you use MySQL, you need to manually download [mysql-connector-java driver][mysql] (8.0.16) and move it to the libs directory of DolphinScheduler
|
||||
which is `api-server/libs/` and `alert-server/libs` and `master-server/libs` and `worker-server/libs`. Let's take MySQL as an example for how to initialize the database:
|
||||
which is `api-server/libs/` and `alert-server/libs` and `master-server/libs` and `worker-server/libs` and `tools/libs`. Let's take MySQL as an example for how to initialize the database:
|
||||
|
||||
For mysql 5.6 / 5.7
|
||||
|
||||
|
||||
@ -86,7 +86,7 @@ https://github.com/apache/dolphinscheduler/tree/dev/dolphinscheduler-api-test/do
|
||||
|
||||
## 补充
|
||||
|
||||
在本地运行的时候，首先需要启动相应的本地服务，可以参考该页面: [环境搭建](https://dolphinscheduler.apache.org/zh-cn/development/development-environment-setup.html)
|
||||
在本地运行的时候，首先需要启动相应的本地服务，可以参考该页面: [环境搭建](./development-environment-setup.md)
|
||||
|
||||
在本地运行 API 测试的时候，可以配置 `-Dlocal=true` 参数，用于连接本地，方便对于 UI 界面的更改。
|
||||
|
||||
|
||||
@ -177,7 +177,7 @@ https://github.com/apache/dolphinscheduler/tree/dev/dolphinscheduler-e2e/dolphin
|
||||
|
||||
## 三、补充
|
||||
|
||||
在本地运行的时候，首先需要启动相应的本地服务，可以参考该页面: [环境搭建](https://dolphinscheduler.apache.org/zh-cn/development/development-environment-setup.html)
|
||||
在本地运行的时候，首先需要启动相应的本地服务，可以参考该页面: [环境搭建](./development-environment-setup.md)
|
||||
|
||||
在本地运行 E2E 测试的时候，可以配置 `-Dlocal=true` 参数，用于连接本地，方便对于 UI 界面的更改。
|
||||
|
||||
|
||||
@ -29,7 +29,7 @@ E2E 测试的主要目的是通过模拟真实的用户场景，验证被测系
|
||||
|
||||
### 如何编写测试代码？
|
||||
|
||||
在认领对应的任务之后，下一步就进入到编写代码的关键。很多同学可能对于 E2E 测试代码并不是很熟悉，因此可以参考该页面：[e2e-test](https://dolphinscheduler.apache.org/zh-cn/development/e2e-test.html)。
|
||||
在认领对应的任务之后，下一步就进入到编写代码的关键。很多同学可能对于 E2E 测试代码并不是很熟悉，因此可以参考该页面：[e2e-test](../e2e-test.md)。
|
||||
|
||||
### 如何提交 Pull Request ？
|
||||
|
||||
|
||||
@ -20,7 +20,7 @@ export SPRING_DATASOURCE_PASSWORD={password}
|
||||
## 伪分布式/分布式安装初始化数据库
|
||||
|
||||
DolphinScheduler 元数据存储在关系型数据库中，目前支持 PostgreSQL 和 MySQL，如果使用 MySQL 则需要手动下载 [mysql-connector-java 驱动][mysql] (8.0.16) 并移动到 DolphinScheduler 的每个模块的 libs 目录下
|
||||
其中包括 `api-server/libs/` 和 `alert-server/libs` 和 `master-server/libs` 和 `worker-server/libs`。下面以 MySQL 为例，说明如何初始化数据库
|
||||
其中包括 `api-server/libs/` 和 `alert-server/libs` 和 `master-server/libs` 和 `worker-server/libs` 和 `tools/libs`。下面以 MySQL 为例，说明如何初始化数据库
|
||||
|
||||
对于mysql 5.6 / 5.7：
|
||||
|
||||
|
||||
@ -50,7 +50,7 @@ Here we show you how to install and run a simple example of pydolphinscheduler
|
||||
### Start Server And Run Example
|
||||
|
||||
Before you run an example, you have to start backend server. You could follow
|
||||
[development setup](https://dolphinscheduler.apache.org/en-us/development/development-environment-setup.html)
|
||||
[development setup](../../docs/docs/en/contribute/development-environment-setup.md)
|
||||
section "DolphinScheduler Standalone Quick Start" to set up developer environment. You have to start backend
|
||||
and frontend server in this step, which mean that you could view DolphinScheduler UI in your browser with URL
|
||||
http://localhost:12345/dolphinscheduler
|
||||
|
||||
@ -25,7 +25,7 @@ and it should be released together with [apache-dolphinscheduler](https://github
|
||||
## To ASF Distribution Directory
|
||||
|
||||
You could release to [ASF Distribution Directory](https://downloads.apache.org/dolphinscheduler/) according to
|
||||
[release guide](https://dolphinscheduler.apache.org/en-us/community/release-prepare.html) in DolphinScheduler
|
||||
[release guide](../../docs/docs/en/contribute/release/release-prepare.md) in DolphinScheduler
|
||||
website.
|
||||
|
||||
## To PyPi
|
||||
|
||||
Loading…
Reference in New Issue
Block a user