Supertokens (self-hosted) with Planetscale as main DB


05/05/2023, 6:10 AM
Newb here, and I am a little unclear on a few things: I am using fastify for my API, and have been able to set up auth and cors as plugins. I am using passwordless only (magic link and social). I have not started building my front end yet. I am hosting supertokens myself, in docker, but separate from my main database, which is using prisma and planetscale. I am unclear as to what the signup flow looks like in this instance. Creating a session and a user etc. I need to be able to protect API routes based on session (using preHandler: verifySession()), and I also need to pass a userID into a lot of the routes. I understand that using auth/signinup will create a user, I just don't know the best approach to add the user to my main DB. Edit: NVM. Looks like the docs give an example that I can make work


05/16/2023, 8:47 AM
Hey, since you mentioned 'planetscale', which you are using as your main DB, can I use supertokens (self-hosted) with planetscale? I tried to use it but planetscale (vitess) does not allow foreign key constraints, So I just want to confirm if that is why you didn't use planetscale instance for supertokens? or is there a work around? Also, can you point to that example you mentioned, please 😄


05/18/2023, 3:20 PM
No idea, I never intended to use supertokens with planetscale, I like to keep auth separate.