-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create first admin user with environment variables at deploy time #9204
Comments
At deployment, there is a default user with credentials |
this is better then nothing but maybe there is a way to do exactly new user as declared in environment? Or at least to plan it doing this way |
I don't know about the way to overwrite first user credentials nor do I know about the plans to make it |
btw SIGN_IN_PREFILLED=true didnt work for me, its anyhow asking for creating new user |
Hey, what's the use-case for this? Maybe there are options but it's hard to tell without context. |
I prefer to have at least server-wide option My intention is to have way to deploy ready-to-use app for providing login details only to some external user with machine up and running and waiting for user to login. |
So you've got 1 server with a multi-tenant setup, or multiple server with 1 tenant on each? |
single self hosted server I want to provide to less advanced person with kind of credentials to access is my goal |
Open the network tab when you signup and you'll see the graphql calls, you can just re-use them :) You can also play around with the graphql console https://twenty.com/developers/graphql/core |
Scope & Context
At initial deployment phase there is no clear way to create admin user
Current behavior
Currently as far as I see there is no way to create new user except of WebUI
Expected behavior
Will be useful to have a kind of variables AUTH_USER/AUTH_PASSWORD to create first user in deploy time. Alternatively if there is a CLI way to do exactly same things, please mention it in documentation more dedicated. Thanks
The text was updated successfully, but these errors were encountered: