Hi folks, I'm creating my instance of supertokens, to handle login in a microservices infrastructure...
e
Hi folks, I'm creating my instance of supertokens, to handle login in a microservices infrastructure. I will deploy the hosted core version, directly inside my infrastructure. There is a way to configure the core via environment variable (i.e licence key, tenant, ecc), instead of doing api calls from my backend?
r
Hey @edubacco
The core takes docker env var for the config
e
Ok so how can I setup 2 different tenant via environment variables? there's documentation somewhere? Thanks 😄
r
ah right. So for tenant creation, thats only via an API call.
e
Ok, and the same for every tenant config I think. Is there an env var for the licence key?
r
there is no env for the license key. However, you can call the API just once and thats saved in the db
e
Ok, we usually work with CD and IaC, so we dislike to have configs directly stored in database, so I'm wondering how to implement a way to have them as code
for example, I create ephemeral environments inside pipelines just to run tests, and the process is completely automated
r
hmm. You could kind of simulate it by figuring out a way to make your "code based config" into an API call on core startup.
But from our side, it will require an API call for teneant creation
e
got it, thanks