Google Git
Sign in
apache / dolphinscheduler-website / HEAD
commit39232a5dbcf017d7340aba9dd7a8e3ba05bc7100[log] [tgz]
authorJay Chung <zhongjiajie955@gmail.com>Mon Jun 16 00:21:50 2025 +0800
committerGitHub <noreply@github.com>Mon Jun 16 00:21:50 2025 +0800
treeebd5fb6b80a14d64a80a9c8e6bbabf47ef72c7dc
parenta9c95171d19985dde584973069ca2e9785ab5f0b [diff]
ci: fix dl failed (#983)

do not know the root cause, but `https://mp.weixin.qq.com` will raise an error in our pipeline,  so maybe we should directly ignore them, because

- if the link work, everything works fine and does not need to change
- if the link do not work, which mean article is delete and can not revert in wechat

```log
2025-06-14T01:14:07.0668795Z /usr/local/lib/node_modules/markdown-link-check/node_modules/async/dist/async.js:325
2025-06-14T01:14:07.0669750Z             if (fn === null) throw new Error("Callback was already called.");
2025-06-14T01:14:07.0670643Z                              ^
2025-06-14T01:14:07.0670896Z 
2025-06-14T01:14:07.0671053Z Error: Callback was already called.
2025-06-14T01:14:07.0672111Z     at /usr/local/lib/node_modules/markdown-link-check/node_modules/async/dist/async.js:325:36
2025-06-14T01:14:07.0673145Z     at /usr/local/lib/node_modules/markdown-link-check/node_modules/async/dist/async.js:249:17
2025-06-14T01:14:07.0674040Z     at /usr/local/lib/node_modules/markdown-link-check/index.js:212:13
2025-06-14T01:14:07.0675247Z     at /usr/local/lib/node_modules/markdown-link-check/node_modules/link-check/lib/proto/http.js:119:21
2025-06-14T01:14:07.0676395Z     at done (/usr/local/lib/node_modules/markdown-link-check/node_modules/needle/lib/needle.js:474:14)
2025-06-14T01:14:07.0677831Z     at PassThrough.<anonymous> (/usr/local/lib/node_modules/markdown-link-check/node_modules/needle/lib/needle.js:734:9)
2025-06-14T01:14:07.0678801Z     at PassThrough.emit (node:events:536:35)
2025-06-14T01:14:07.0679383Z     at endReadableNT (node:internal/streams/readable:1698:12)
2025-06-14T01:14:07.0680201Z     at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
```
1 file changed
tree: ebd5fb6b80a14d64a80a9c8e6bbabf47ef72c7dc
  1. .github/
  2. blog/
  3. config/
  4. events/
  5. img/
  6. public/
  7. scripts/
  8. src/
  9. .asf.yaml
  10. .dlc.json
  11. .gitignore
  12. .htaccess
  13. HOW_PREPARE_WORK.md
  14. LICENSE
  15. package.json
  16. README.md
  17. yarn.lock
README.md

Apache DolphinScheduler Official Website

This project keeps all sources used for building up DolphinScheduler's official website which is served at https://dolphinscheduler.apache.org/.

Build Website Locally

  1. Run yarn in the root directory to install the dependencies.
  2. Run commands to collect resources 2.1. Run export PROTOCOL_MODE=ssh tells Git clone resource via SSH protocol instead of HTTPS protocol 2.2. Run ./scripts/prepare_docs.sh prepare all related resources, for more information you could see how prepare script work
  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.
  1. 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.
  2. Verify your change locally: python -m SimpleHTTPServer 8000, when your python version is 3 use :python3 -m http.server 8000 instead.

If you have higher version of node installed, you may consider nvm to allow different versions of node coexisting on your machine.

  1. Follow the instructions to install nvm
  2. Run nvm install v18.12.1 to install node v18
  3. Run nvm use v18.12.1 to switch the working environment to node v18

Then you are all set to run and build the website. Follow the build instruction above for the details.

How to send a PR

  1. Do not use git add . to commit all the changes.
  2. Just push your changed files, such as:
    • *.md
    • blog.js or docs.js or site.js
  3. Send a PR to master branch.

SEO

Make sure each .md starts with the following texts:

---
title: title
keywords: keywords1,keywords2, keywords3
description: some description
---

Guide for adding a new document

Add a new blog

  1. Add new .md file under blog/en-us or blog/zh-cn.
  2. Update site_config/blog.js, add a new entry to the blog in either en-us or zh-cn.
  3. Run docsite start locally to verify the blog can be displayed correctly.
  4. Send the pull request contains the .md and blog.js only.

Best Regards.
Thanks for reading :)