From 9cb2413dffa204278c889e9ea89be86bad2df2f5 Mon Sep 17 00:00:00 2001 From: Tim Gates Date: Fri, 19 Feb 2021 08:57:04 +1100 Subject: [PATCH] Fix a few small typos --- README.md | 4 ++-- example/kubernetes/using-secrets/README.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 21ace0f..7e54a40 100644 --- a/README.md +++ b/README.md @@ -153,7 +153,7 @@ Do not edit slapd.conf it's not used. To modify your server configuration use ld #### Seed ldap database with ldif This image can load ldif files at startup with either `ldapadd` or `ldapmodify`. -Mount `.ldif` in `/container/service/slapd/assets/config/bootstrap/ldif` directory if you want to overwrite image default boostrap ldif files or in `/container/service/slapd/assets/config/bootstrap/ldif/custom` (recommended) to extend image config. +Mount `.ldif` in `/container/service/slapd/assets/config/bootstrap/ldif` directory if you want to overwrite image default bootstrap ldif files or in `/container/service/slapd/assets/config/bootstrap/ldif/custom` (recommended) to extend image config. Files containing `changeType:` attributes will be loaded with `ldapmodify`. @@ -393,7 +393,7 @@ Replication options: Other environment variables: - **KEEP_EXISTING_CONFIG**: Do not change the ldap config. Defaults to `false` - if set to *true* with an existing database, config will remain unchanged. Image tls and replication config will not be run. The container can be started with LDAP_ADMIN_PASSWORD and LDAP_CONFIG_PASSWORD empty or filled with fake data. - - if set to *true* when bootstrapping a new database, bootstap ldif and schema will not be added and tls and replication config will not be run. + - if set to *true* when bootstrapping a new database, bootstrap ldif and schema will not be added and tls and replication config will not be run. - **LDAP_REMOVE_CONFIG_AFTER_SETUP**: delete config folder after setup. Defaults to `true` - **LDAP_SSL_HELPER_PREFIX**: ssl-helper environment variables prefix. Defaults to `ldap`, ssl-helper first search config from LDAP_SSL_HELPER_* variables, before SSL_HELPER_* variables. diff --git a/example/kubernetes/using-secrets/README.md b/example/kubernetes/using-secrets/README.md index a9e916e..a28eba0 100644 --- a/example/kubernetes/using-secrets/README.md +++ b/example/kubernetes/using-secrets/README.md @@ -2,6 +2,6 @@ `make example` -Then edit the yaml files in the environment directory to have the desired paraneters, and then make the secret file: +Then edit the yaml files in the environment directory to have the desired parameters, and then make the secret file: `make ldap-secret.yaml`