Is there any update on mongodb support?
# support-questions-legacy
m
Is there any update on mongodb support?
r
Hey. Nothing on it yet. We haven’t planned any work on mongodb support for the foreseeable future.
m
Got it. So the current status is that login with mongo does not work, what does that mean? Thanks for the quick response
My understanding is that upon login the user info is not stored in the mongodb?
r
recipes like email password, third party, passwordless won't work with mongo (the apis wil return a 500 error)
only session recipe works with mongodb
m
Ah I see. Thanks for the info
r
You can sign up for our managed service though. That way, you won’t need to setup mysql / psql on your end for supertokens
m
Got it my setup needs mongo (or any nosql). In an ideal world I was hoping to self host everything so that potential users of my app could also self host if need be. But that may not be possible
r
whats your use case here? Maybe there is another solution out. When you say "potential users of my app could also self host if need be", do you mean that your customers can deploy your software on their stack too?
m
Yea it’s a bit weird sorry. I’m developing metadata management app for academic science. Since it’s academic, the ability for users to deploy the app themselves is appealing
r
I see. If you could allow them to deploy their app on their own, except for the auth part, which you have deployed, would that work? So each of your customers would connect their self deployed software to a supertokens core that you control in your infra (connected to a psql).
m
Ah I see. Perhaps. I’m relatively new to web dev, but I’m curious if I could manage users in psql and then keep everything else in nosql?
r
yup. That can be done for sure.
supertokens would only store the user ID and the credentials of the user. You would get this user ID in the post sign up override via the supertokens SDK, and then store all user data against this user ID in mongo
furthermore, if you host the core yourself, you can tell your customers to connect to your supertokens core from their self deployed solution. So they would just need to self depoly mongo and still get everything to work
it's just that you would have to deploy psql on your end for the core. Thats all (or you can use our managed service for the core, and then you don't even have to do that)
m
Okay awesome thanks for the info, this could be a good way for me. As for deploying the core, I could just use your docker?
r
yup. You could
just one thing, you would want to create one app in the core per customer of yours (so that their user pools are all isolated), and this is a paid feature.
m
Oh I see. So if my user wanted to deploy they app, they couldn’t deploy their own core?
r
they could, but they would then need psql alongside it. If you want them to not add psql to their stack, then they could connect to a core hosted by you, in which you create a user pool / app for them to connect to.
the first method (if they host their own core with psql) is free. The second method (ability for you to create multiple apps in the core) is paid.
6 Views