# Documentation DOCU-169 - Improve documentation for configuration variables to include allowed values

Project: Documentation
Status: closed
URL: https://community.openproject.org/work_packages/DOCU-169

## OPEN POINTS

_No work packages_

## People

| Attribute | Value |
| --- | --- |
| Assignee | Adam Szabo |
| Accountable |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work |  |
| Remaining work |  |

## Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Date |  |
| % Complete |  |
| Category |  |
| Target versions |  |
| Priority | Medium |
| List |  |

## Costs

| Attribute | Value |
| --- | --- |
| Overall costs |  |
| Labor costs |  |
| Unit costs |  |
| Spent units |  |

## Description

The current documentation of environment variables is poor in that sense that they don't really say

<https://www.openproject.org/docs/installation-and-operations/configuration/>

  - what they do, what they are good for (no links to more detailed guides)
  - it is incomplete as `OPENPROJECT_EDITION` is missing for example
  - in cases when there is only a closed set of options allowed, those options are not documented. Only the defaults are explained.  `OPENPROJECT_EDITION` would need to be documented to have `standard` as default and `bim` as another option, for example.

The List of Configuration Variables that could be overridden by defining them in the Environment could be listed with the following command:

<https://community.openproject.org/projects/gmbh/wiki/2nd-level-support-knowledge-base#get-a-list-of-all-configuration-variables-that-can-be-overridden-by-defining-them-in-the-environment-from-bash>