You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Bernd Ahlers 4fa0c2cb2b Add changelog for 2.4.7 10 months ago
.github Update issue template (#144) 3 years ago
graffles sidecar overview update 3 years ago
images Replace huge animated GIF with 2 smaller PNG screenshots (#410) 1 year ago
includes Add missing includes directory 3 years ago
pages Add changelog for 2.4.7 10 months ago
.gitignore Updated README (#452) 1 year ago
.mailmap Add .mailmap file 5 years ago
.travis.yml Adding command line parameter turning warnings into errors. 3 years ago Rename LICENSE to 4 years ago
Makefile Do not watch the .git directory contents and also ignore "*~" files 3 years ago Updated README (#452) 1 year ago added lib to exclude 1 year ago
index.rst Move security related docs into their own section (#450) 1 year ago
requirements.txt Add Python virtualenv and sphinx-autobuild (#72) 3 years ago

The Graylog documentation

Build Status


This is the repository that is used to create running at readthedocs. After changes are pushed to the specific branches, the new pages are built automatically. When the build runs without error, the new pages are available after some minutes.

The typical workflow to make changes to the documentation and preview them before you push the changes to this repository needs the following preparation.

  • clone the repository (to your workplace)
  • initialize the virtual environment for python
  • install the required python packages

After the above is done, changes can be made and previewed with the following

  • create git branch for your changes
  • change to the virtual environment
  • make the modifications/additions
  • run the build and check for errors
  • push the branch to GitHub and create a pull request

Now a review of the changes is needed and, finally, it will be merged by the reviewer into the branch/version of the documentation you created the pull request for. Should the change be available in other versions of the documentation this should be written in the pull request that the reviewer can push this to the specific versions too.

Building locally

required software

  • git
  • python (including pip)
    • virtualenv (pip install virtualenv)
  • make
  • browser (to preview)

Mac & Linux

It is very likely that you already have all needed software available. If not we recommend homebrew for Mac and the package manager of the Linux distribution you are using.

first time preparation

Clone the repository to your workbench:

# git clone 

Create and enter the python virtual environment:

# cd documentation
# virtualenv .
# source ./bin/activate

Install Sphinx, the theme we are using, and sphinx-autobuild:

# pip install -r requirements.txt


For Windows we recommend chocolatey to install the requirements. If that is not possible to use, download and install the software from the project webpages.

Windows Installation in detail

This can not be a complete guide, but this might give you some guidance.

Installation the needed software using chocolatey. Github Desktop and Notepad+ are optional, but a good addition. The commands need to be run in your administrator Powershell.

# choco install python
# choco install git
# choco install make
# choco install github-desktop
# choco install notepadplus

Use the Github Desktop application to clone the repository, by default this can be found in C:\Users\$USERNAME\Documents\GitHub\$REPONAME. Or you run git clone in your Workbench directory.

Open Powershell at this location and enable your user to run scripts:

# Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy Bypass -Force;

Use the python package manager pip to install virtulenv. Create the virtual environment, change into the environment and install all requirements:

# pip install virtualenv
# virtualenv .
# .\Scripts\activate
# pip install -r requirements.txt

Once the above is done you are prepared to contribute to the documentation and preview the work live in your local browser. See the daily usage chapter.

daily usage

How to work with git, create branches and push them will not be covered in this document. Change into the prepared directory, update the sources (git pull), change into the virtual python environment (Linux/Mac source ./bin/active, Windows .\Scripts\activate) and start making the changes.

Build the static documentation and open them in your browser:

# make html
# open _build/html/index.html

Build the documentation and automatically build them on any change:

# make livehtml
# open