Closed mwickett closed 1 month ago
Ok, this was an interesting experience. The actual Clerk specific part wasn't too bad - swapping out keys, updating webhook endpoints etc. The surprising (and in retrospect it shouldn't have been surprising) is that configuring oauth social logins (like Google) is a good amount of effort.
For now, I'm just going with email / password auth because I have a bunch of hoops to jump through to setup a Google application to be able to enable logging in with your Google account.
Need to take care of this, but I'm kinda holding off for now because I feel like the chances of some data loss are still high if we evolve the schema a bit more as planned. Taking Clerk to production just feels like a rubicon, although I haven't inspected that feeling in any tangible way, and should do that.
It's a bit of a trade-off here because getting better at making decent sized changes through actual reasonable migrations is a good and this is practice, but also it's just way easier to move fast right now being ok with some data loss right now.