you can change the

resetPasswordFeature

style in the config change the style?

hi guys, question on self hosting the supertokens core. how is the memory usage? I plan on running this on ec2 t3 micro alongside postgres + an express backend. would it be sufficient?

Usually the core uses 300-400 mb RAM at rest (thanks to the JVM). On heavy load (250rps), it can go up to 500 mb. If you deploy 5 of these instances and put a load balancer in front, you can easily achieve 1000rps consistently. The thread pool size should be equal to the number of (virtual) cores in the ec2 instance

oh no, I probably won't need that many rps and scale horizontally

thanks for the info

cool!

you can also limit the heap size (when running our start command) to reduce the 250 mb usage. See https://supertokens.io/docs/thirdpartyemailpassword/common-customizations/cli/start

@User , to answer your question in more detail, you can have a look at this: https://supertokens.io/docs/auth-react/emailpassword/config/reset-password Specifically, try to use the

submitNewPasswordForm

>

style

object.

Hi @User , I have a function which I run on sign up/in. I currently make it run by checking if

context.action === "SUCCESS"

, now I also want to run this function on logout event, how can I go about doing that?

which version of the node SDK are you using?

I am doing it in the frontend, should have mentioned that.

supertokens-auth-react: ^0.14.1

supertokens-node: ^5.0.1

ah right.. on the frontend, you want to override the signOut function mentioned here: https://supertokens.io/docs/auth-react/0.14.X/session/override/functions

This is how it's done: https://supertokens.io/docs/thirdpartyemailpassword/advanced-customizations/frontend-functions-override/usage

I followed this for adding a function post sign up/in: https://supertokens.io/docs/thirdpartyemailpassword/common-customizations/handling-signinup-success

Added it inside a onHandleEvent in init

Yea so in the version of the SDK that you are using, there is no sign out event (it's there in the 0.15.X though. So in your version, you can capture that by using the override feature in session.init and overriding the signOut function

Okay, so upgrading to the 0.15.X isn't recommended?

oh.. you can! for sure..

and then there is a sign out event that's fired as mentioned here: https://supertokens.io/docs/session/advanced-customizations/frontend-hooks/handle-event

Got it. So I upgrading to 0.15.0, do I have to upgrade supertokens-node to a newer version too?

nope

Understood, thank you for quick response.

The function doesn't run on adding

context.action === "SIGN_OUT"

, I have upgraded supertokens-auth-react to 0.15.0.

Can I see the full init code please?

message has been deleted

right.. the SIGN_OUT event is fired in the Session.init()

All I have done is added an OR statement.