search

ParachuteTeam / Parachute

🪂 Parachute.fyi is an open-sourced web-based scheduling application built with modern frameworks. It integrates modern user interface and login mechanism, thus offering way better experience than when2meet.com.
https://parachute.fyi
MIT License
12 stars 4 forks source link

Switch to clerk for auth? #85

Open louisunlimited opened 1 year ago

louisunlimited commented 1 year ago

Next Auth seems kinda unstable and I'm now questioning stability when pushed to production. We've sure all experienced setbacks when using it in dev, for ex this:

Screenshot 2023-07-19 at 13 17 38

So here I propose using a third party auth service like Clerk.dev. It's free for < 5000 MAUs, which I think is pretty reasonable, and I've used it myself when building CS411 project and it seems reliable.

@RaymondWHZ @HaiyueZhang @pastezzz Thoughs?

RaymondWHZ commented 1 year ago

The concept of this product is excellent. In this way, we can allow users to register by email directly as they wish, and maybe it can provide a better way to manage SSO providers and users.

The question is: how does it store user information? On its own platform? Besides, how should we change our current session feature and database adaptor?

louisunlimited commented 1 year ago

The concept of this product is excellent. In this way, we can allow users to register by email directly as they wish, and maybe it can provide a better way to manage SSO providers and users.

The question is: how does it store user information? On its own platform? Besides, how should we change our current session feature and database adaptor?

@RaymondWHZ Yes! We will let Clerk to handle all the storing/auth-ing of user info. We will need to remove all our db adapters and stuff form our current project since we don't need them anymore. So after this our db will be ONLY used for storing actual event logistics and such.

RaymondWHZ commented 1 year ago

The concept of this product is excellent. In this way, we can allow users to register by email directly as they wish, and maybe it can provide a better way to manage SSO providers and users. The question is: how does it store user information? On its own platform? Besides, how should we change our current session feature and database adaptor?

@RaymondWHZ Yes! We will let Clerk to handle all the storing/auth-ing of user info. We will need to remove all our db adapters and stuff form our current project since we don't need them anymore. So after this our db will be ONLY used for storing actual event logistics and such.

Great! I think we can proceed with this idea.