resholve
lldap
Our great sponsors
resholve | lldap | |
---|---|---|
11 | 76 | |
208 | 3,499 | |
- | 6.2% | |
7.7 | 9.1 | |
7 days ago | 2 days ago | |
Python | Rust | |
MIT License | 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.
resholve
-
What is the Flakes version of "reproducible interpreted scripts"?
I'm also not 100% on whether it answers the question, but I imagine you're thinking of https://github.com/abathur/resholve (doc in nixpkgs: https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/misc/resholve/README.md)
-
modular bash profile scripting with shellswain
I intend to eventually find some time to figure out how feasible it would be to use https://github.com/abathur/resholve or wrapper techniques to bolt basalt (and perhaps other bash PMs) on to the nix ecosystem and nix-package some of your libraries.
-
Is there a good way to programmatically determine how many inputs some function can support?
(I'd love to have this ability for https://github.com/abathur/resholve to reliably identify arguments to one command that are also external commands/programs that it will in turn exec. I can't imagine trying to start it until/unless I have any bright ideas about how that executable spec and a parser for it would work.)
-
Could someone give me an example how I would have multiple "commands" in default.nix?
In https://github.com/abathur/resholve/blob/master/default.nix and https://github.com/abathur/resholve/blob/master/shell.nix you can see one approach to extending that line of thought to the default.nix itself.
-
Building the Future of the Command Line
Completions have in general been of interest, though the shell-specific completions I've looked at so far were all too dynamic.
I'd forgotten all about Fig since I saw your launch post here last year, so thanks for reminder. (I don't think I had quite started to work on parsing specific external commands, yet. Was still focused on just identifying the likely presence of exec in the executables.)
Are you familiar with the parse code? Are you handling painful stuff like combined short flags with a trailing option? (If I ferreted out some of the more painful cases I've had to wrangle, I am curious if you'd have a gut sense of whether your approach handles it. Would you mind if I reach out? I am working on this for https://github.com/abathur/resholve)
-
Devbox: Instant, easy, and predictable shells and containers
@dloreto @robrich A little aside from the announcement, but since it seems like you both work on this I wanted to surface something that came up down in a subthread:
I'm curious if you attempted to support macOS by doing this with Nix's dockerTools and cross-compiling (there may be better sources, but it's at least hinted at in https://nix.dev/tutorials/building-and-running-docker-images...)? If so, I'm wondering where that failed or bogged down?
---
Background: I build a tool (https://github.com/abathur/resholve) for ~packaging Bash/Shell (i.e., for demanding all dependencies be present). The tool's technically agnostic, but I built it specifically to fix Shell packaging in Nix.
I think it could benefit a lot of other Shell projects, since one of Shell's big tribulations is dealing with heterogenous environments, but most Shell projects wouldn't see much reason to endure the pain of adopting Nix if they still had to support the heterogenous environments.
Much like you're doing here, I've entertained figuring out how to build a Nix-based packaging flow that can generate deployable standalone bundles or containers. It'd be a heavy way to bundle Shell, but I imagine some projects would take the tradeoff for predictability and reduced support load. But since it would need to take place within a Nix build, I'd need to cross-compile for it to work on macOS. Hoping you know if it's a dead-end or not :)
-
Ask HN: Why aren't code diagram generating tools more common?
For a concrete example, I've been developing a tool (https://github.com/abathur/resholve) that can ~build/link Bash/Shell scripts--i.e., rewrite them with external executables converted to absolute paths. (This helps ensure dependencies are known, declared, present, and don't have to be on the global PATH for the script to execute cleanly.)
There's a devilish sub-problem, which is that any given executable can potentially exec arbitrary arguments. For now I handle this with a very crude automated binary/executable analysis that needs to be augmented by human source analysis. Deep multi-language source analysis wouldn't be very scalable, but I suspect fairly-standardized structural annotations could improve the results in a scalable way.
I have to imagine there are other applications of the same information.
-
I wrote an article about creating unit-tests and mocks for POSIX shells
I'm not 100% sure if you see the minimal PATH dependencies as a problem or not--so this may or may not help--but I develop https://github.com/abathur/resholve to make it easier to package Shell in Nix/nixpkgs by rewriting invocations of external dependencies in Shell scripts to absolute paths--and shunit2 is one of the Nix packages that I've updated to use resholve.
-
On Env Shebangs
I came here to say this, too :)
But, of course, it still isn't a silver bullet...
1. You still have to have a sane PATH. A fair amount of the Nix install-related issues that get opened are PATH problems, and you can also run into problems with PATH in cron/launchd.
2. You still have to know what the script depends on. This can get tricky beyond small scripts you wrote yourself. (I write a tool for ~linking/resolving external dependencies in Shell scripts, https://github.com/abathur/resholve. As I've been working on converting some of nixpkgs' existing Shell packages to use it, I almost always find dependencies the initial packager missed.)
-
Runtime dependencies for a bash script
Check out resholve. https://github.com/abathur/resholve
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?
datashare - A self-hosted search engine for documents.
glauth - A lightweight LDAP server for development, home use, or CI
mpack - MPack - A C encoder/decoder for the MessagePack serialization format / msgpack.org[C]
ntfy - Send push notifications to your phone or desktop using PUT/POST
egglog0 - Datalog + Egg = Good
awesome-selfhosted - A list of Free Software network services and web applications which can be hosted on your own servers
devbox - Instant, easy, and predictable development environments
authentik - The authentication glue you need.
py_regular_expressions - Learn Python Regular Expressions step by step from beginner to advanced levels
PropertyWebBuilder - Create a fully featured real estate website on Rails in minutes! ⛺
swift-sh - Easily script with third-party Swift dependencies.
pwm - pwm