“SaaS (hosted by us)” -> “Create an App” results in HTTP 404

@User i am not able to reproduce this error. Can you give more details about this please?

Turns out it happens on my iPhone but web is fine😬

oh! strange

Ah i see. Thanks! Will fix this.

Fixed!

Hello! I just stumbled upon supertokens by looking through auth examples in Next.js. I am quite intrigued by the features and architecture diagram I am seeing so far. A hesitation I am currently feeling is the fact that the service is written in Java. I have tons of experience working on Java spring services for my job and I know java can be a memory hog. From what I can tell this server does not use spring but I was wondering if there were any sizing recommendations or performance benchmarks to see memory usage/cpu usage?

We are able to run one instance of a core to achieve 200 requests per second with AWS's t3.micro instance.

And since the core is stateless, you can add more instances of that behind a load balancer.

Nice!!

I am also assuming if I want to build my own login ui in react that is possible as well?

Yup. You can call the APIs yourself too. The API spec that your frontend should use is found here: https://supertokens.io/docs/fdi Alternatively, you can embed our react components into your react app anywhere, override specific components in our component tree, run any JS to modify parts of our UI, or change the CSS as per your liking

I’d assume yes, Just like in react native.

I have worked with too many component systems that don't allow overrides of most things and it's so frustrating. It's so nice to find something that actually is open source and fully configurable 😄

My many years of working with bad tech is making me cynical 😢

Haha. Fair enough. Have a look at this: https://supertokens.io/docs/thirdpartyemailpassword/advanced-customizations/react-component-override/usage

It is truly a very humble library/service with an exceptionally great DX

Thank you @User . :))

Credit, where credit is due 😉

Only 200 requests?!?

Totally not fast a sync

200 requests per second. That’s quite high. You would need couple of 100 thousand active users for that

To add to this, the majority of auth requests will be for session verification. This does not require the core and happens within the SDK itself. So to make the 200 reqs / second to the core would require a very high number of MAUs with a very low session expiry

I was looking at the overrides documentation and I completely agree. It's like replacing a method with another.

I have my supertokens docker behind a nginx docker and I'm setting up ssl through DigitalOcean certs with lets encrypt. Is there a way I can do this and end up with https without giving my server a domain name. I want to just go to https on the ip through the port 80 of the reverse proxy

I think that is possible based on https://support.globalsign.com/ssl/general-ssl/securing-public-ip-address-ssl-certificates

Also, if you are using https, you should use port 443 and not port 80

Interesting mkay

Is it easier to add a domain name? Maybe to keep it inside the digital ocean setup cleanly?