lldap VS restic

The architecture of an IAM platform is made up of 3 layers: the base infrastructure layer, the application layer, and the connection layer. The base layer is composed of a directory store, a repository for identity information, and synchronization, the ability for multiple directories to share identity information with each other. There were many self-hosted LDAP directory servers available, like the 389 Directory Server and FreeIPA, but I chose LLDAP to be the centralized directory store because of its simple configuration and low resource usage.

A new LLdapDockerComposeConnectionDetailsFactory class for Light LDAP Implementation for Authentication.

Good to hear, I think it'll make many users happy. For me, I've migrated back to Authelia. I moved to authentik because at the time Authelia had no user management. After all of authentik's sharp edges, I've found lldap[0], and was able to implement a pilot in a few hours. I haven't looked back, since everything was converted.

[0]: https://github.com/lldap/lldap

I wrote LLDAP (https://github.com/lldap/lldap) after struggling to install and configure openLdap on my homelab.

I've recently installed and configured LLDAP (Lightweight LDAP) - More details here if you've never heard of it before: GitHub - lldap/lldap: Light LDAP implementation

I've an LLDAP instance running to make managing users easier.

Used to be restic[1], but I switched to kopia[2]. For Android I just sync /storage/emulated/0/ with syncthing. All devices are backed up to a home server. Home server backups go to Backblaze (but any S3-compatible storage would do).

1. https://restic.net/

For anyone looking to migrate off borg because of this, append-only is available in restic, but only with the rest-server backend:

https://github.com/restic/restic

https://github.com/restic/rest-server

which has to be started with --append-only. I use this systemd unit:

  [Unit]

Run restic to backup an entire filesystem or a subset of it, and upload to a remote S3-compatible storage.

Restic is my personal favorite for straightforward file backups. It's simple and well-designed, integrates with rclone meaning it supports any cloud storage service you can imagine, and has a decently large community surrounding it.

https://restic.net/

https://github.com/rubiojr/awesome-restic

Let me show you how I back up my computers with restic and rclone using simple systemd configuration.

Afaik not yet, there was some discussion here: https://github.com/restic/restic/issues/804

For me, these traits made restic initially attractive:

- encrypted, chunk-deduped, snapshotted backups

- single Go binary, so I could even backup the binary used to create my backups

- reasonable versioning and release scheme

- I could read, and understand, its design document: https://github.com/restic/restic/blob/master/doc/design.rst

I then just tried using it for a year and never hit any issues with it, so kept going, and now it's 6+ years later.