Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bitnami/openldap] Add documentation for OpenLDAP directory persistence #76697

Closed
najose opened this issue Jan 28, 2025 · 3 comments · Fixed by #76785
Closed

[bitnami/openldap] Add documentation for OpenLDAP directory persistence #76697

najose opened this issue Jan 28, 2025 · 3 comments · Fixed by #76785
Assignees

Comments

@najose
Copy link
Contributor

najose commented Jan 28, 2025

Name and Version

bitnami/openldap (all versions)

What is the problem this feature will solve?

I could not find documentation regarding persistence of data for the OpenLDAP container. The examples seems to use /bitnami/openldap as the mountpoint for data volumes. Looking at the Dockerfile, there seems to be the LDAP_VOLUME_DIR environment variable which also points to this same path. Is the recommended path if so, can this be added to the docs. I can work on adding it the docs if it will be accepted after a review.

export LDAP_VOLUME_DIR="/bitnami/openldap"
export LDAP_DATA_DIR="${LDAP_VOLUME_DIR}/data"

What is the feature you are proposing to solve the problem?

Document the path where LDAP data is persisted.

What alternatives have you considered?

No response

@github-actions github-actions bot added the triage Triage is needed label Jan 28, 2025
@javsalgar
Copy link
Contributor

Hi!

Thank you so much for the request! Indeed, contributions are welcome, so we would be grateful if you submitted a PR. If not, we will work on it but we cannot guarantee an ETA as it is not a critical fix.

@najose
Copy link
Contributor Author

najose commented Jan 30, 2025

@javsalgar, Cool, I've opened a PR for this at #76785

@javsalgar
Copy link
Contributor

Thank you so much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants