dani
/
lemonldap-ng
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix doc markup

This commit is contained in:
Maxime Besson 2022-09-07 11:41:28 +02:00
parent ef3b19ea18
commit 4e0e8b6061
4 changed files with 11 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/sources/admin/checkstate.rst
View File

@ -33,9 +33,9 @@ The plugin will respond to the HTTP request with:
* HTTP code 500 if something went wrong * HTTP code 500 if something went wrong
* HTTP code 200 and the following JSON content if something went right * HTTP code 200 and the following JSON content if something went right
``` .. code:: json
{"result":1,"version":"2.0.14"}
``` {"result":1,"version":"2.0.14"}
.. versionadded:: 2.0.14 .. versionadded:: 2.0.14
The *version* key is returned The *version* key is returned

6
doc/sources/admin/portalcustom.rst
View File

@ -137,11 +137,9 @@ To achieve this, you can create a rule in the Manager: select
skin is applied. skin is applied.
- **Value**: the name of the skin to use. - **Value**: the name of the skin to use.
Example: Example::
``` $_url =~ m#^http://test1.example.com#
$_url =~ m#^http://test1.example.com#
```
Skin files Skin files
~~~~~~~~~~ ~~~~~~~~~~

4
doc/sources/admin/ssoaas.rst
View File

@ -47,9 +47,9 @@ Two different kinds of architecture are existing to do this:
Some requests can be dropped by the central FastCGI/uWSGI server. Some requests can be dropped by the central FastCGI/uWSGI server.
Example below with an uWSGI server to prevent Load Balancer health check requests Example below with an uWSGI server to prevent Load Balancer health check requests
being forwarded to the central DevOps Handler: being forwarded to the central DevOps Handler ::
```route-remote-addr = ^127\.0\.0\.25[34]$ break: 403 Forbidden for IP ${REMOTE_ADDR}``` route-remote-addr = ^127\.0\.0\.25[34]$ break: 403 Forbidden for IP ${REMOTE_ADDR}
Example of a Central FastCGI architecture: Example of a Central FastCGI architecture:

12
doc/sources/admin/upgrade_2_0_x.rst
View File

@ -186,17 +186,13 @@ LemonLDAP::NG version is returned by the CheckState plugin
If you use the `/checkstate` URL to monitor LemonLDAP::NG, you may notice a slight change in the output format: If you use the `/checkstate` URL to monitor LemonLDAP::NG, you may notice a slight change in the output format:
*2.0.13* : *2.0.13* ::
``` {"result":1}
{"result":1}
```
*2.0.14* : *2.0.14* ::
``` {"result":1,"version":"2.0.14"}
{"result":1,"version":"2.0.14"}
```
Depending on your load balancer or monitoring configuration, this can cause false negatives. Depending on your load balancer or monitoring configuration, this can cause false negatives.