Documentation for building the documentation for ...
This doc is intended for maintainers and regular contributors to
the project. The README.md
doc covers the basic steps for one-off
builds from the master
branch.
In all cases, the version number and release string do not need to be manually specified, though the directions do provide steps for doing so in at least one case.
Directions in this doc provide examples for building HTML and epub formats. See
the official http://www.sphinx-doc.org/en/stable/invocation.html doc for other
formats that Sphinx is capable of building. Some formats may require
installation of other packages for your operating system that are not
installed by following the current setup/prep directions in the
README.md
file.
These steps guide you through the steps necessary to build a version of the docs that match those hosted on rsyslog.com or that are available via distro packages.
These directions assume that 8.33.0
is the latest stable release version.
Substitute the actual latest stable release version as you follow the
steps in this document.
- These directions are generalized as the specific steps are highly dependent on the production build/hosting environment.
- All steps provided are intended to be run from the maintainer's dev workstation.
- Review the
README.md
file for instructions that cover installingpip
, setting up the virtual environment and installing the latest version of the Sphinx package. - Clone the https://github.com/rsyslog-doc.git repo
- Merge
master
into the current stable branch (e.g.,v8-stable
) - Tag the stable branch
- Push all changes to the remote
- Run the
release_build.sh
script - Sync the contents of the
build
directory over to the web server - Sync the latest release doc tarball to where the previous release tarball is hosted. Update references to this tarball as necessary.
You have several options:
- Download the release tarball (http://www.rsyslog.com/download/download-v8-stable/)
- Download a zip file from GitHub
- Clone GitHub repo and checkout the latest stable tag
- Decompress the tarball
- Change your current working directory to that of the directory containing
the
source
directory,README.md
and other content that was within the tarball- For example,
cd /tmp/rsyslog-8.33.0
(thersyslog-8.33.0
folder is within the tarball)
- For example,
- Run
sphinx -b html source build
You may need to first follow the directions in the README.md
doc to create or activate your virtual environment if the sphinx
package
is not already installed and known to your installation of Python.
- Visit https://github.com/rsyslog/rsyslog-doc
- Click on 'Branch: master' and choose 'Tags' from the right-column
- Select the
v8.33.0
tag - Click on the 'Clone or download' green button to the far right
- Click 'Download ZIP' and save the file to your system
- Decompress the zip file
- Change your current working directory to that of the directory containing
the
source
directory,README.md
and other content that was within the tarball.- For example,
cd C:\users\deoren\Downloads\rsyslog-8.33.0
(thersyslog-8.33.0
folder is within the tarball)
- For example,
sphinx -D version="8.33" release="8.33.0" -b html source build
- You have to specify the
version
andrelease
values here for now because we do not modify thesource/conf.py
file in the stable branch or its tags to hard-code the new version number.
- You have to specify the
You may need to first follow the directions in the README.md
doc to create or activate your virtual environment if the sphinx
package
is not already installed and known to your installation of Python.
- Review the
README.md
file for instructions that cover installingpip
, setting up the virtual environment and installing the latest version of the Sphinx package. - Run
git clone https://github.com/rsyslog-doc.git
- Run
git checkout v8.33.0
- Run
sphinx -D version="8.33" release="8.33.0" -b html source build
You may need to first follow the directions in the README.md
doc to create or activate your virtual environment if the sphinx
package
is not already installed and known to your installation of Python.
You have several options for obtaining a snapshot of the branch you would
like to build (most often this is the master
branch):
- Download a zip file from GitHub
- Clone GitHub repo using Git
We do not (currently) build tarballs ourselves for in-development snapshots of the docs.
These directions assume that you wish to build the docs from the master
branch. Substitute master
for any other branch that you wish to build.
- Follow the steps previously given for downloading the zip file from GitHub, this time substituting the tag download option for the branch you wish to obtain doc sources for.
- Decompress the zip file and change your current working directory to that path.
- Run
sphinx -D release="dev-build" -b html source build
to generate HTML format andsphinx -b epub source build
to build an epub file.
These directions assume that you wish to build the docs from the master
branch. Substitute master
for any other branch that you wish to build.
The Sphinx build configuration file will attempt to pull the needed information from the Git repo in order to generate a "dev build" release string. This release string is prominently displayed in various places throughout the docs and is useful to identify a dev build from a release set of documentation.
- Review the
README.md
file for instructions that cover installingpip
, setting up the virtual environment and installing the latest version of the Sphinx package. - Run
git clone https://github.com/rsyslog-doc.git
- Run
git checkout master
- Run
sphinx -b html source build
to generate HTML format andsphinx -b epub source build
to build an epub file.