aight, just wanted to get that down, thank you!

also, how does one go about scaling this? since everything's persisted in the database, I can just spawn multiple supertokens-core and put a load balancer in front of it? then just make sure all of these supertokens-core instances are pointing to a single master db?

Yes.

And you don't need to put a load balancer since the NodeSDK uses a round robin method anyway

but you can always do that... yea

I don't have to worry about sticky sessions or anything like that?

u don't

so no ephemeral data stays in the supertokens-core?

nothing.

demn, that's awesome, have been always a pain to handle

hmm, when was this page pushed? xD https://supertokens.io/docs/session/appinfo

would be nice if the properties had jsdoc annotations on them so it integrates nicely with the IDE, and I think you can also auto-generate the SDK API docs with that?

agreed.

You could create a PR for this if you'd like :))

haha, will look into the codebase when I find the time and see if it's quick to do and readability won't suffer these days the last time I did one, the lines of each file got pretty lengthy and the average line comments is around 60% lol

Is there anyway to persist a session between different subdomains? We have a few different subdomains and it seems logging in the main one and redirecting is not doing the trick. Or can we do that with any specific setting?

Yea. You can. Are the sub domains using the same top level domain?

yea they are.. that's why it;s called a sub domin haha.. my bad

1 min

Have a look at: https://supertokens.io/docs/thirdpartyemailpassword/common-customizations/sessions/share-sessions-across-sub-domains

yes!

Thanks! Will test now. In case of nextJS, do I need to add the same recipe for node-js or only on react will do?

you can continue using the same recipe you are using right now

Have a look at this link: https://supertokens.io/recipe-redirect?to=/common-customizations/sessions/share-sessions-across-sub-domains You can ignore the previous one..

I have tested here and put live, but it didn't work. When I go to the subdomain it asks for a new login.

Can you share the frontend config + an example of the a sub domain being used?

Front-end config:

export const frontendConfig = () => {
  return {
    useReactRouterDom: false,
    appInfo,
    recipeList: [
      Session.init({
        sessionScope: ".offscript.io",
      }),
      ThirdPartyEmailPasswordReact.init({
        signInAndUpFeature: {
          providers: [
            ThirdPartyEmailPasswordReact.Google.init(),
            ThirdPartyEmailPasswordReact.Facebook.init(),
          ],
      }),
      SessionReact.init(),
    ],
  }
}

Also appinfo is:

const appInfo = {
  appName: "Off Script",
  apiDomain: websiteDomain,
  websiteDomain,
  apiBasePath: "/api/auth/",
}

WebsiteDomain is

my.offscript.io

and

offscript.io

according to the domain.

set the websiteDOmain to always be

offscript.io

when I did that, the subdomains could not login, that's why I kept different. It threw a CORS error

Ah. You should keep it to offscript.io, and what the CORS error?