so basically everything except intelliJ works correctly

Ohh ok, thank you, really helpful, going to try that these days, and let you know in case I need any help @User

thanks @User for your help :))

Is there anyway to contribute with the documentation? I'd like to send to current NextJS documentation how we implemented the same procedures in Typescript

At the moment, the docs is in a private repo :(. We wanted to make it in a public repo, but haven't gotten around to doing it.

I'll see what I can do about this in a few days.. will try and make the website OSS as well.

or at least the docs section

cool

Hi, How can access zenhub to know what you are working on?

Not sure if zenhub allows to make public projects. I’ll have to look into it..

Installing the extension I could already see the Board!

Oh! I’ll check it out

@User you can ask questions here about contributing.

@adarsh1497 is here? 🙂

okay

yeah this one https://github.com/supertokens/supertokens-core/issues/275 https://discordapp.com/channels/603466164219281420/603500538029539350/876458234771275828

That issue has already been assigned and has multiple PRs. Have you seen them and the comments in them?

ohh yes just saw

Right. So feel free to contribute to those PRs.. if u get stuck anywhere, you can ask questions here.

okay thanks

For anyone who wants to use windows to contribute, you can use wsl2: https://docs.microsoft.com/en-us/windows/wsl/about

Setting up dev env on my Macbook Pro (M1 chip), facing the following issues. Let me know if anyone else has resolved this earlier docker build -t supertokens . --platform linux/x86_64 runs successfully docker run --platform linux/x86_64 -p 3567:3567 supertokens throws below error

runtime: failed to create new OS thread (have 2 already; errno=22)
fatal error: newosproc

runtime stack:
runtime.throw(0x524da0, 0x9)
        /usr/local/go/src/runtime/panic.go:527 +0x90
runtime.newosproc(0xc820026000, 0xc820035fc0)
        /usr/local/go/src/runtime/os1_linux.go:150 +0x1ab
runtime.newm(0x555ce8, 0x0)
        /usr/local/go/src/runtime/proc1.go:1105 +0x130
runtime.main.func1()
        /usr/local/go/src/runtime/proc.go:48 +0x2c
runtime.systemstack(0x5c4300)
        /usr/local/go/src/runtime/asm_amd64.s:262 +0x79
runtime.mstart()
        /usr/local/go/src/runtime/proc1.go:674

goroutine 1 [running]:
runtime.systemstack_switch()
        /usr/local/go/src/runtime/asm_amd64.s:216 fp=0xc820020770 sp=0xc820020768
runtime.main()
        /usr/local/go/src/runtime/proc.go:49 +0x62 fp=0xc8200207c0 sp=0xc820020770
runtime.goexit()
        /usr/local/go/src/runtime/asm_amd64.s:1696 +0x1 fp=0xc8200207c8 sp=0xc8200207c0

Used the linux-arm jre to fix this

On this page: https://supertokens.io/docs/thirdparty/quick-setup/backend At step: 7) Setup the SuperTokens core I think the yes/no should be swapped?

How so? The yes implies that you are using

try.supertokens.io

and you will need to register to get a connection uri for your own use

Maybe after clicking yes the documentation should explain that while you can use the URL for demo purposes you will need to register etc? If that makes it clearer

I see. I thought clicking yes means you are trying the demo URL and no means you have your own URL (either managed or self-hosted).

The step is titled "Setup..." so if I specify that I am using

try.supertokens.io

(clicking yes) i would expect there to be nothing for me to do because that's the demo URL which is already setup, right?

Yeah I suppose the messaging can be made clearer, saying that if you’re just trying it out no more steps are required. And if you want to prepare for an app you plan to release you need to register