fragile_frogs

I have been asking this myself for a while now, I generally do enjoy writing SQL, but I also get the feeling that it's not suitable for building applications.

So why is there no "functional" query language? Something like Haskell, but for databases. You would get the benefits of a declarative model, composeability and type-safety.

I am currently using sqlx[1] and it's great in terms of type-safety, but you can't compose queries. I don't like to use ORM's, they are usually good for simple things, but hard things are impossible and you have to use/understand SQL anyways.

[1] https://github.com/launchbadge/sqlx

Hey folks ,

I am currently redesigning the landing page of my open source project which you can find here: https://auth.vulpo.dev/

I am still in the process of figuring out what content I should put on the landing page and I was wondering, what are you looking for when you evaluate an open source project?

I have already covered a few minor things that are important to me:

- Current Version

- Link to Guides | API docs | GitHub

- Demo of the product: Code and UI Example

What else is important to you?

Hey folks, Michael here.

I have been working in this project on and of for about a year and a half and I finally got it into a state where I can share it. I initially started this project to learn Rust and afterwards decided to make it useful for others.

Vulpo Auth is an authentication server that you can host yourself. The goal was to make it as easy as possible for you to get started and have a complete authentication solution without you having to configure anything. Project Website: https://auth.vulpo.dev

The Project contains: - Auth Server (Rust) - Admin Dashboard - JS and react SDK - Prebuilt Web UI (currently react) (https://auth.vulpo.dev/ui) - rust SDK for rocket

Some of the features: - Email and Password Auth - Passwordless Auth - Google Auth - Translateable Email Templates - Enable/Disable Sign In or Sign Up - Password Reset Flow - Update Email Flow

There is still a lot to do, the code base is full of experimental ideas and there a bunch of things to clean up, but first I want to focus on writing documentation and guides before adding more features.

Besides the missing documentation, what are you missing?