nimsearch
lldap
nimsearch | lldap | |
---|---|---|
2 | 76 | |
10 | 3,499 | |
- | 3.7% | |
2.6 | 9.1 | |
11 months ago | 6 days ago | |
Nim | Rust | |
- | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nimsearch
-
Self Hosted SaaS Alternatives
You are welcome. Thanks are too rarely offered. :-)
You may also be interested in word stemming ( such as used by snowball stemmer in https://github.com/c-blake/nimsearch ) or other NLP techniques, but I don't know how internationalized/multi-lingual that stuff is, but conceptually you might want "series of stemmed words" to be the content fragments of interest.
Similarity scores have many applications. Weights on graph of cancelled downloads ranked by size might be one. :)
Of course, for your specific "truncation" problem, you might also be able to just do an edit distance against the much smaller filenames and compare data prefixes in files or use a SHA256 of a content-based first slice. ( There are edit distance algos in Nim in https://github.com/c-blake/cligen/blob/master/cligen/textUt.... as well as in https://github.com/c-blake/suggest ).
Or, you could do a little program like ndup/sh/ndup to create a "mirrored file tree" of such content-based slices then you could use any true duplicate-file finder (like https://github.com/c-blake/bu/blob/main/dups.nim) on the little signature system to identify duplicates and go from path suffixes in those clusters back to the main filesystem. Of course, a single KV store within one or two files would be more efficient than thousands of tiny files. There are many possibilities.
-
Ask HN: Books about full text search
It's all in the Nim programming language, but if you prefer reading code or running diffs then you might get a vague sense of (some) low level nuts & bolts from: https://github.com/c-blake/nimsearch
lldap
-
Keycloak SSO with Docker Compose and Nginx
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
-
Ask HN: What apps have you created for your own use?
I wrote LLDAP (https://github.com/lldap/lldap) after struggling to install and configure openLdap on my homelab.
-
Anyone else using LLDAP and if so... (can it do TrueNAS & Linux User/Login authentication?)
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
- Lldap Release 0.5.0
-
🆕 Cosmos 0.8.0 - All in one secure Reverse-proxy, container manager and authentication provider has a brand new App Marketplace to share compose file! Also added home customization
I've an LLDAP instance running to make managing users easier.
- Simple AD for testing stuff in homelab?
-
LDAP resources/recommendations question
I'm trying to integrate LDAP into my small homelab but I'm extreme noobie in it. So far I've tried: 1. OpenLDAP - not so resource heavy but I found it difficult go get working correctly with NextCloud, Keycloak and Jellyfin. Maybe someone could recommend an easy to follow guide? 2. LLDAP - honestly it's almost prefect. Nice clean UI, great guides how to setup with everything I need, but it's a read-only LDAP, so I cannot create or manage users with Keycloak or NC, that's about the only downside and probably bugs me more than it should. 3. 389ds - has everything I need (and probably some more), super easy to setup with this guide but the elephant in the room is that it uses 700MiB of RAM (whereas LLDAP uses only 7-8MiB). That's a big difference which really makes me question whether I want to use this particular solution.
-
Keycloak – Open-Source Identity and Access Management Interview
Note that if you want to use KeyCloak for the OpenID but want to still have a LDAP source of truth, you can use LLDAP + KeyCloak together, with LLDAP as the source of truth and KeyCloak giving you the fancy features: https://github.com/lldap/lldap/blob/main/example_configs/key...
- 🆕 Cosmos 0.6.0 - All in one secure Reverse-proxy, container manager and authentication provider now supports OpenID! Guides available in the documentation on how to setup Nextcloud, Minio and Gitea easily from the UI.
-
How do you organize accounts and passwords in your self-hosted environment?
To be fair, their respective documentations (here and here) are pretty comprehensive.
What are some alternatives?
suggest - An mmap-persistent Wolfe Garbe's SymSpell spell checking algorithm in Nim
glauth - A lightweight LDAP server for development, home use, or CI
awesome-selfhosted - A list of Free Software network services and web applications which can be hosted on your own servers
ntfy - Send push notifications to your phone or desktop using PUT/POST
vector-search - The definitive guide to using Vector Search to solve your semantic search production workload needs.
Compose-Examples - Various Docker Compose examples of selfhosted FOSS and proprietary projects.
authentik - The authentication glue you need.
ndup - Near-Duplicate File Detection
PropertyWebBuilder - Create a fully featured real estate website on Rails in minutes! ⛺
home-ops - Wife approved HomeOps driven by Kubernetes and GitOps using Flux
pwm - pwm