images/ldap
7
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

Fix errors in README

Browse source
This commit is contained in:
paul 2019-05-15 18:28:41 +02:00
parent 85837fc860
commit 475b4ad0f7
1 changed files with 17 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

24
README.md
View file

@ -4,7 +4,16 @@ services.
Therefore, a lot of services have a direct (or indirect) dependency on this Therefore, a lot of services have a direct (or indirect) dependency on this
image. image.
### Getting the image
This image is automatically build and pushed to the docker hub. Therefore
getting the image should be as easy as running
```
docker pull zombi/ldap
```
### Building slapd ### Building slapd
It is also possible to manually build this image from this repository.
``` ```
docker build -t zombi/ldap . docker build -t zombi/ldap .
@ -25,14 +34,15 @@ docker-compose up -d
``` ```
### Backing up data ### Backing up data
Data in this container is considered essential, since it influences almost State stored in this container is essential to many other services, that
all other services we run. use authentication and authorization. Therefore you should think about
backing up the LDAP database in regular intervals.
We recently discovered that **simply copying all the data from `data` DOES **simply copying all the data from `data` MAY NOT WORK**, as there could
NOT WORK**, therefore we included scripts for backing up the slapd database be race conditions leading to database corruption during the backup.
into a compact .ldif format. The recommended way is to use the included script for backing up the database
into a compact .ldif plain text file.
running `tools/create-ldap-backup.sh` will create two files: running `contrib/create-ldap-backup.sh` will create two files:
* `conf.ldif` is a backup of the configuration. * `conf.ldif` is a backup of the configuration.
* `data.ldif` contains all the saved datasets. * `data.ldif` contains all the saved datasets.