mirror of
https://github.com/lldap/lldap.git
synced 2026-04-25 08:15:52 +03:00
[GH-ISSUE #339] Static file backend #127
Labels
No labels
backend
blocked
bug
cleanup
dependencies
docker
documentation
duplicate
enhancement
enhancement
frontend
github_actions
good first issue
help wanted
help wanted
integration
invalid
ldap
pull-request
question
rust
rust
tests
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/lldap-lldap#127
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @rlex on GitHub (Oct 18, 2022).
Original GitHub issue: https://github.com/lldap/lldap/issues/339
Hello! First of all, thanks for project.
I wonder if there is plans to implement file-based user DB?
glauth (https://github.com/glauth/glauth) have nice example (but project looks pretty much abandoned):
It can be useful on small install (labs, selfhosted stuff, etc). One idea is to run multiple pods in k8s reading from single configmap to achieve at least some level of HA without need for external DB.
@nitnelave commented on GitHub (Oct 18, 2022):
I'm having trouble relating your requirements: small deploys, but HA?
If you want small-scale stuff, then (file-based) SQLite works very well.
If you really want HA then you could have a bunch of read-only mirrors of the SQLite file and it should work fine (special master for modifications, lots of read only slaves).
But then if you want HA it seems that having a simple postgres or even MySQL would be simpler, no? LLDAP itself is stateless so you can point many to the same DB.
If that's what you want, then there's an issue for supporting other DBs
@nitnelave commented on GitHub (Oct 19, 2022):
(https://github.com/nitnelave/lldap/issues/87)