Tarantool documentation source, published at https://www.tarantool.io/doc/.
See Docker
First of all, pull the image for building the docs.
docker pull tarantool/doc-builder:fat-4.3Next, initialize a Makefile for your OS:
docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.3 sh -c "cmake ."A big part of documentation sources comes from several other projects, connected as Git submodules. To include their latest contents in the docs, run these two steps.
Update the submodules:
git submodule update --init git fetch --recurse-submodules git submodule update --remote --checkout
This will initialize Git submodules and update them to the top of the stable branch in each repository.
git submodule updatecan sometimes fail, for example, when you have changes in submodules' files. You can reinitialize submodules to fix the problem.Caution: all untracked changes in submodules will be lost!
git submodule deinit -f . git submodule update --initNote that there's an option to update submodule repositories with a
makecommand. However, it's intended for use in a CI environment and not on a local machine.docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.3 sh -c "make pull-modules"
Build the submodules content:
docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.3 sh -c "make build-modules"
This command will do two things:
- Generate documentation source files from the source code
- Copy these files to the right places under the
./doc/directory.
If you're editing submodules locally, repeat this step to view the updated results.
Now you're ready to build and preview the documentation locally.
When editing the documentation, you can set up a live-reload server. It will build your documentation and serve it on 127.0.0.1:8000. Every time you make changes in the source files, it will rebuild the docs and refresh the browser page.
docker run --rm -it -p 8000:8000 -v $(pwd):/doc tarantool/doc-builder:fat-4.3 sh -c "make autobuild"First build will take some time. When it's done, open 127.0.0.1:8000 in the browser. Now when you make changes, they will be rebuilt in a few seconds, and the browser tab with preview will reload automatically.
You can also build the docs manually with make html, and then serve them using python3 built-in server:
docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.3 sh -c "make html"
docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.3 sh -c "make html-ru"
python3 -m http.server --directory output/htmlor python2 built-in server:
cd output/html
python -m SimpleHTTPServerthen go to localhost:8000 in your browser.
There are other commands which can run in the tarantool/doc-builder container:
docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.3 sh -c "make html"
docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.3 sh -c "make html-ru"
docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.3 sh -c "make singlehtml"
docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.3 sh -c "make singlehtml-ru"
docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.3 sh -c "make pdf"
docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.3 sh -c "make pdf-ru"
docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.3 sh -c "make json"
docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.3 sh -c "make json-ru"
docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.3 sh -c "make epub"
docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.3 sh -c "make epub-ru"
docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.3 sh -c "make update-po"There's a specific build mode which checks internal and external links instead of producing a document.
docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.3 sh -c "make linkcheck"If you need to save the linkcheck's report in a file, you can use the following trick:
docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.3 sh -c "make linkcheck" 2>&1 | tee linkcheck.logHere 2>&1 redirects the stderr output to stdout, and then tee both shows in on screen and writes to a file.
Tarantool documentation uses the Vale linter for checking grammar, style, and word usage. Its configuration is placed in the vale.ini file located in the root project directory.
To enable RST support in Vale, you need to install Sphinx. Then, you can enable Vale integration in your IDE, for example:
Terms:
- translation unit (TU) is an atomic piece of text which can be translated. A paragraph, a list item, a heading, image's alt-text and so on.
- translation source files are the files with translation units in English only. They're located in
locale/en. - translation files are the files which match original text to translated text. They're located in
locale/ru.
To update the translation files, run the make update-po task:
docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.3 sh -c "make update-po"Translate the strings in the updated files and then commit the changes.
To contribute to documentation, use the REST format for drafting and submit your updates as a pull request via GitHub.
To comply with the writing and formatting style, use the guidelines provided in the documentation, common sense and existing documents.
Notes:
- If you suggest creating a new documentation section (a whole new page), it has to be saved to the relevant section at GitHub.
- If you want to contribute to localizing this documentation (for example, into Russian), add your translation strings to
.pofiles stored in the corresponding locale directory (for example,/locale/ru/LC_MESSAGES/for Russian). See more about localizing with Sphinx at http://www.sphinx-doc.org/en/stable/intl.html.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent