wagi
lldap
Our great sponsors
wagi | lldap | |
---|---|---|
14 | 76 | |
867 | 3,344 | |
1.3% | 3.7% | |
1.8 | 9.2 | |
almost 2 years ago | 9 days ago | |
Rust | Rust | |
Apache License 2.0 | 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.
wagi
-
Reminiscing CGI Scripts
WAGI and WCGI are the WASM based spiritual successors.
-
A simple web server written in Awk
Compile a CGI program in any language to WASI, then use https://github.com/deislabs/wagi to run it.
-
Running WASI binaries from your HTML using Web Components
Yeah of course! They've got STDIN/STDOUT/STDERR and I've built a Virtual Filesystem. But if you're using WASI binaries locally they don't have that restriction.
You might be interested in WAGI: https://github.com/deislabs/wagi
And to catch up on WASI: https://xeiaso.net/talks/unix-philosophy-logical-extreme-was...
-
Waggy, the library for writing WAGI API handlers in Go
As I'm sure you've heard, WASM has been growing in popularity and use over the past few years. And with the creation of WASI (Web Assembly System Interface) and WAGI (Web Assembly Gateway Interface), WASM is starting to venture outside of running just in the browser. And in the case of WAGI, if you've been programming since the earlier days of the internet, it might feel very similar to CGI programming (and that's because it's based on CGI1.1!) WAGI provides a way for developers to define handlers for HTTP requests and route them to specific functions inside of, or entire, WASM modules. It does so by piping the headers of the incoming request to os.Args[1:], piping the body of the incoming request to os.Stdin, and writing the response to os.Stdout. (To learn more about configuring, routing, compiling, and deploying WAGI routes, as well as the limitations of WAGI routes, please consult the WAGI docs and the TinyGo WASM docs)
-
Rethinking Virtualization for Back Ends
What do you think of WAGI [1], which is basically CGI for WASM modules.
[1]: https://github.com/deislabs/wagi/blob/main/docs/writing_modu...
- Isolates, MicroVMs, and WebAssembly (In 2022)
-
The Promise of WASM
as serverless functions (https://github.com/deislabs/wagi)
-
Single Page Applications using Rust (with WASM)
I'm experimenting with WASM & Rust but with a different framework named wagi, there's a great video by Rainer Stropek & Stefan Baumgartner that gives a little introduction to it [0]
-
Building a WebAssembly-powered serverless platform
Krustlet and WAGI are two such projects.
-
Running AssemblyScript in Kubernetes with Krustlet
However there is some cool ideas from DeisLabs around something called WAGI. This is, as they call it, just an experiment but it's essentially applying WASI to CGI (hence the name). If CGI was a bit before your time, it was a way in which web handlers were handled by CLI scripts. Reading posts from stdin and replying with stdout. There's a lot of reason we don't use that anymore but with WASI running in Kubernetes that becomes a lot more appealing and interesting again. I really think that this is a fantastic improvement on the container situation and I hope we can see more development in this space.
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.
I have Authelia running for 2+ years already. I configured it with LDAP using "LLDAP" [0], a lightweight LDAP implementation. I then use Caddy as a reverse proxy and integrate it [1] with Authelia. This works great. I have solid 2FA for all my services and I feel my self-hosted applications are secure enough to be accessed without VPN. My only concern is that Authelia hasn't had a new release for more than a year, which raises security concerns.
-
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.
-
🆕 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.
-
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
I tried Keycloak for my homelab, but I found the ressource usage especially on startup to be too high (3 GB memory or something) and since I wanted minimal sever footprint I went with lldap[1] as the user store and authelia[2] to do forward auth using traefik.
Pretty happy with this setup, though it has less features than Keycloak, it's easier to administrate from code.
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.
-
LDAP or AD for selfhosted
https://github.com/lldap/lldap is a very simple and lightweight LDAP solution. Works flawless with https://www.authelia.com/
-
Anything you wish there was an open source solution for?
I know this isn't what you're looking for, but I've checked out https://github.com/lldap/lldap in the past and think it's pretty neat.
What are some alternatives?
glauth - A lightweight LDAP server for development, home use, or CI
ntfy - Send push notifications to your phone or desktop using PUT/POST
wasi-experimental-http - Experimental outbound HTTP support for WebAssembly and WASI
awesome-selfhosted - A list of Free Software network services and web applications which can be hosted on your own servers
wasmer-python - 🐍🕸 WebAssembly runtime for Python
authentik - The authentication glue you need.
PropertyWebBuilder - Create a fully featured real estate website on Rails in minutes! ⛺
pwm - pwm
idm - LibreGraph Identity Management
authelia - The Single Sign-On Multi-Factor portal for web apps
create-rust-app - Set up a modern rust+react web app by running one command.
yunohost - YunoHost is an operating system aiming to simplify as much as possible the administration of a server. This repository corresponds to the core code, written mostly in Python and Bash.