You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As an anythingllm administrator attempting to deploy a number of anythingllm environments, I currently need to set the admin username and password for the initial Admin user in each environment manually before I can create the API key and use the API to configure the needed users, workspaces and other features for that environment.
I'd like to have a fully-automated and hands-off deployment option, and this is one of the main manual steps blocking me from achieving this.
I will file other issues for a couple other things needed for fully-automated deployments.
The text was updated successfully, but these errors were encountered:
@timothyasp if you'd prefer I'll rename this to enable automated deployment for multi-user environments. I wasn't sure how much content you would like in one FR so I started it out at a granular level.
If anything, in my mind this request makes sense as just one FR, because they are all really close in scope since if we enable multi-user on boot you probably also want to make users and such - let's just keep it one issue for now and if scope grows then we can break it out where it makes sense 👍
ajferrario
changed the title
[FEAT]: Add Admin username and password support to the initial configuration options during deployment
[FEAT]: Enable multi-user on boot
Jul 15, 2024
What would you like to see?
As an anythingllm administrator attempting to deploy a number of anythingllm environments, I currently need to set the admin username and password for the initial Admin user in each environment manually before I can create the API key and use the API to configure the needed users, workspaces and other features for that environment.
I'd like to have a fully-automated and hands-off deployment option, and this is one of the main manual steps blocking me from achieving this.
I will file other issues for a couple other things needed for fully-automated deployments.
The text was updated successfully, but these errors were encountered: