https://supertokens.com/ logo
Join Discord
Powered by
What would be the next step?
# general
d
What would be the next step?
p
What would be the next step?
So you have the DB running and your backend configured?
d
so i need back and frontend right
i have mysql installed but no db or so setup
ive downloaded the python backend files
p
yeah, you should have both back and frontend. you can complete the setup for backend without having a frontend though.
d
Alright
p
do you want to run the core yourself or would you want to use a hosted version?
d
self hosted
p
you can then check out the quick setup -> core -> self hosted section of the docs about running the core
you can do with/without docker which is one decision point. I'd suggest going with docker and using the in-memory db first to test things.
d
so now
i have the docker container running i guess
oh wait
what is the name of the container?
so i can stop it
now the core is running
p
well I think the name is auto generated if you didn't set one
the image is 
supertokens-mysql
I think
d
for the backend
do i need to download the example?
prob. easier right?
p
You can do it that way, but I'd just copy and paste from the quick setup guide
d
on the form
what do enter under api domain, path and website, domain path
p
api domain is where the backend will be available, e.g.: http://localhost:3001
website path is where the frontend will be served e.g.: http://localhost:3000
and the 2 paths are optional, they are basically for customization purposes
d
but the API Domain is the ip and port for the core right?
OOoo
it is what the api and domain will be
i think i actually did smth wrong
i have the mysql setup with the databse and tables, i ran the docker container (the core) and then there should be like mydomain:3567/hello but its not working
oh wait
i also need to enter the connection url in the python backend
p
yeah, but the 
/hello
should work without the backend
that is served by the core docker container
d
weird o.O
p
can you check if the container is still running/ maps the port?
d
its up
p
so if you check "localhost:3567/hello" it times out? or connection refused?
d
It says Connection Refused
p
hmm, even with localhost?
d
i cant check localhost :/
but wait
p
you can still run curl and wget on the server
d
docker run -p 3567:3567 -e MYSQL_USER="root" -e MYSQL_PASSWORD="password" -e MYSQL_HOST="localhost" -e MYSQL_PORT="3306" -e MYSQL_DATABASE_NAME="supertokens" -d registry.supertokens.io/supertokens/supertokens-mysql
is that right?
like with MYSQL_HOST="localhost"
p
It looks correct
is mysql running?
so on the same machine where you are running the core you can: 
curl http://localhost:3567/hello
because the reason you can't connect to it may be that your server doesn't allow connection to this port from the outside, which is fine if the backend will be running on the same host.
d
hmhm wait
8 Views
PreviousNext
Powered by