Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #1869] [FEAT]: Add API Key support to the initial configuration options during deployment, and possibly add it to the API #1218

New Issue
Closed
opened 2026-02-22 18:23:45 -05:00 by yindo · 1 comment
yindo commented 2026-02-22 18:23:45 -05:00
Owner
Copy Link
Copy Source

Originally created by @ajferrario on GitHub (Jul 15, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1869

What would you like to see?

As an anythingllm administrator attempting to deploy a number of anythingllm environments, I currently need to create an API Key for the initial Admin user in each environment manually before I can 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.

Adding it to the API would be for enabling other users to use anythingllm without ever having to use the GUI.

I will file other issues for a couple other things needed for fully-automated deployments.

Originally created by @ajferrario on GitHub (Jul 15, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1869 ### What would you like to see? As an anythingllm administrator attempting to deploy a number of anythingllm environments, I currently need to create an API Key for the initial Admin user in each environment manually before I can 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. Adding it to the API would be for enabling other users to use anythingllm without ever having to use the GUI. I will file other issues for a couple other things needed for fully-automated deployments.
yindo added the enhancementfeature request labels 2026-02-22 18:23:45 -05:00
yindo closed this issue 2026-02-22 18:23:45 -05:00
yindo commented 2026-02-22 18:23:45 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jul 15, 2024):

Duplicate of #1870

@timothycarambat commented on GitHub (Jul 15, 2024): Duplicate of #1870
yindo changed title from [FEAT]: Add API Key support to the initial configuration options during deployment, and possibly add it to the API to [GH-ISSUE #1869] [FEAT]: Add API Key support to the initial configuration options during deployment, and possibly add it to the API 2026-06-05 14:39:33 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label enhancement feature request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#1218
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?