Our latest documents are in directory docs DolphinScheduler main repository, and the history documents before version 3.0.0-alpha is in branch history-docs in website repository. In this case, you have to collect them from above repository into current working path before you compile them to HTML.
Of course, you could collect all content manually, but we already provider convenience script to do that, all you have to do is run a single command in this project root directory:
./scripts/prepare_docs.sh
Note: The default protocol to fetch repository from GitHub is via HTTPS. When you failed to run the command above and see some log like “unable to access” in your terminal, or if you feel clone via HTTPS is a little slow. You can switch clone protocol to SSH by change the environment variable by execute command
export PROTOCOL_MODE=sshin your terminal. The next time you execute command./scripts/prepare_docs.shwill user protocol SSH instead of HTTPS, which is more stable and fast in some cases, such as local development
After the command finished, all prepare things you need to start DolphinScheduler website is being done.
After version 3.0.0-alpha, our release document is in repository apache/dolphinscheduler directory docs. Documentation and code will be released together, so when the new version is released, we need to get the corresponding documentation from the released tag.
All you have to do it is add/change variable DEV_RELEASE_DOCS_VERSIONS in conf.sh. For example, if you want to add new release docs named 10.0.0 and its docs in apache/dolphinscheduler branch 10.0.0-release, you could add a new key-value to DEV_RELEASE_DOCS_VERSIONS
declare -A DEV_RELEASE_DOCS_VERSIONS=( ... ["10.0.0"]="10.0.0-release" ... )
A few days later, you find out version 10.0.0's document has a bug. You fix it and push it to apache/dolphinscheduler branch 10.0.0-release to fix the bug, you could keep your configuration in the old content.
declare -A DEV_RELEASE_DOCS_VERSIONS=( ... ["10.0.0"]="10.0.0-release" ... )