Makes sense! We are working on it already 🙂

Awesome! Thanks! 😄

hii

I liked to ask for any guide to install supertoken on ubuntu linux vps

the docker file is good and all

but its also a good idea to let user managed the database. Sometimes the tights couplings of service and database can be hard to manage and costly when not needed

We do let users manage the database @User

Hi, I want to install the service on premise in my k8s cluster... do you publish the chart to any helm repo -- or i just use the github repo?

Helm chart

Has anyone integrated supertokens with an aws-cdk app?

I am going through some nodejs samples but I see a lot of express code.

I am not using a framework for backend at the moment. Do I have to use express with lambda in order to use supertokens? 😅

@bhumilsarvaiya Akshay here.

Aws lambda

Is there a chance that

supertokens-website

could be made more functional in nature? I'm starting to see that for SSR frameworks (e.g., Svelte-Kit, Next, Nuxt, Remix),

SuperTokens.init()

can get a little difficult because

window.fetch

needs to exist. But

window

doesn't exist on the backend. It doesn't make sense to call

SuperTokens.init()

from within another frontend function that's intended to be used multiple times (because then

init

would be called several times when it only needs to be called once). So it has to be used in a more "open" area. But

SuperTokens.init()

also can't easily be placed in a location that's too open or the SSR aspect of the framework will error out due to

window

being

undefined

. If it was more functional, maybe a function could be returned that grabs all the things we need (e.g., modifications to fetch)? I'm not sure how feasible that is. Or perhaps there are workarounds to the problem that I haven't considered. But many of these workarounds seem a bit hackish/unorthodox.

Or maybe a new

supertokens-ssr

🤔

@XxX_MLG Noob_XxX we will consider making it compatible with SSR, but on the server side. However, it will take some time. In the meantime, we ask people to do something like this on the global scope:

if (typeof window !== "undefined") {
  supertokens.init({...})
}

is it possible to do a combination (passwordless, email, social) that is not a current recipe?

Recipe combination

Makes sense. Thanks!

is the core service layer scalable or rather how is it scalable? i may have missed that reading through the documentation

does anyone have a concrete example of advanced customization for the React components? either advanced customization or using rolling your own? that would be very much appreciated.

Okay. I've been working on this for awhile. It still is not finished, and it can probably be improved upon. But here's my running example of using

Remix

with `SuperTokens`: https://github.com/ITenthusiasm/remix-supertokens Does SuperTokens ever review this kind of stuff? If it's written correctly, it should enable people to get auth up and running without end users needing to enable JavaScript. It might also give new ideas for the default forms exported by SuperTokens. If it's written incorrectly or I'm missing any use cases / error cases (specifically within login/signup/resetting passwords), I can try to fix those. 🙂 The 2 things I hope to add in the future are specified in the TODO list. (They are JS-enhanced forms and a local db example... if I find time.)

What are some common design patterns that community is following for refreshing tokens?

refresh token patterns

What is the scope of email feature(currently and in the near future roadmap)? There's already an email service in my app used for other emails, should I use that or use the one provided by SuperTokens.

Hey @sharma can you ask future questions in the support-questions channel?

Email service

What's the best way to handle an invite workflow? We've got an app that lets users invite other users. Email and password only. When a user is invited we don't want the inviter to have to set a password for the invitee (the invitee should set it when they accept the invite). It'a a Next.js app with an existing GraphQL API, so I'm hoping to use the SuperToken Node.js SDK and just swap-out the implementations for the exisiting mutations I've got (

invitePerson

,

acceptInvite

,

resetPassword

etc). Also, we've got our own email service (email templates as well as sending method), so just looking to generate tokens that we can use to construct our own links.