ray/doc
2022-01-25 10:52:53 -08:00
..
azure Revert "[docs] Clean up doc structure (first part) (#21667)" (#21763) 2022-01-20 15:30:56 -08:00
kubernetes Revert "[docs] Clean up doc structure (first part) (#21667)" (#21763) 2022-01-20 15:30:56 -08:00
source [RFC] [Core] Support disabling log redirection via RAY_LOG_TO_STDERR environment variable. (#21767) 2022-01-25 10:52:53 -08:00
tools Revert "[docs] Clean up doc structure (first part) (#21667)" (#21763) 2022-01-20 15:30:56 -08:00
yarn Revert "[docs] Clean up doc structure (first part) (#21667)" (#21763) 2022-01-20 15:30:56 -08:00
.gitignore [docs] new structure (#21776) 2022-01-21 15:42:05 -08:00
BUILD [docs] new structure (#21776) 2022-01-21 15:42:05 -08:00
make.bat Get Sphinx infrastructure in place 2016-07-01 18:21:02 -07:00
Makefile [docs] new structure (#21776) 2022-01-21 15:42:05 -08:00
README.md [docs] new structure (#21776) 2022-01-21 15:42:05 -08:00
requirements-doc.txt [docs] integrate algolia docsearch, move to sphinx panels (#21814) 2022-01-24 17:00:41 -08:00
requirements-rtd.txt [docs] new structure (#21776) 2022-01-21 15:42:05 -08:00

Ray Documentation

Repository for documentation of the Ray project, hosted at docs.ray.io.

Installation

To build the documentation, make sure you have ray installed first. For building the documentation locally install the following dependencies:

pip install -r requirements-doc.txt

Building the documentation

To compile the documentation and open it locally, run the following command from this directory.

make html && open _build/html/index.html

Building just one sub-project

Often your changes in documentation just concern one sub-project, such as Tune or Train. To build just this one sub-project, and ignore the rest (leading to build warnings due to broken references etc.), run the following command:

DOC_LIB=<project> sphinx-build -b html -d _build/doctrees  source _build/html

where <project> is the name of the sub-project and can be any of the docs projects in the source/ directory either called tune, rllib, train, cluster, serve, raysgd, data or the ones starting with ray-, e.g. ray-observability.

Announcements and includes

To add new announcements and other messaging to the top or bottom of a documentation page, check the _includes folder first to see if the message you want is already there (like "get help" or "we're hiring" etc.) If not, add the template you want and include it accordingly, i.e. with

.. include:: /_includes/<my-announcement>

This ensures consistent messaging across documentation pages.

To check if there are broken links, run the following (we are currently not running this in the CI since there are false positives).

make linkcheck

Running doctests

To run tests for examples shipping with docstrings in Python files, run the following command:

make doctest