Cozy Auth MVP #234
jehrhardt
started this conversation in
Official RFCs
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This proposal defines the scope of the Cozy Auth MVP, from which we can continue to build.
Context
There has been a lot of experiments around Cozy Auth. We started with Supapasskeys as a pure Supabase extension developed with the Phoenix framework and Elixir. We tried different approaches around developing it in Rust instead. Over time we learned a lot that will help us to finally develop a working product.
It is time to get this working product out and let people really use it.
Proposal
To reduce Cozy Auth on the minimum of features that make it usable and hopefully viable to early adopters, we need to cover the following basics:
The development will happen in a monorepo, where page, docs and examples are together with the actual code. The implementation of features can therefore cover everything in a single pull request. A Typescript SDK will get its own monorepo.
Benefits
The focus on self-hosting Cozy Auth reduces the scope of development significantly, while it can still provide a useful solution for people willing to spend some extra effort.
This is a highly efficient way to get something out.
Implementation
Beta Was this translation helpful? Give feedback.
All reactions