-
Notifications
You must be signed in to change notification settings - Fork 26
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
🚀 Enhancement: Create Organisation using CLI #130
Open
2 tasks done
Aarush-Acharya opened this issue
Jun 15, 2024
· 4 comments
· May be fixed by appwrite/sdk-generator#912
Open
2 tasks done
🚀 Enhancement: Create Organisation using CLI #130
Aarush-Acharya opened this issue
Jun 15, 2024
· 4 comments
· May be fixed by appwrite/sdk-generator#912
Labels
enhancement
New feature or request
Comments
On Appwrite version 1.6, the user will be able to initialize a team. I have confirmed this successfully creates a team by using the following command and pushing it to the Appwrite Console.
|
@choir27 this looks great |
@FatahChan great work |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🔖 Enhancement description
Allow creation of an organisation using CLI
🎤 Pitch
I work for an Open Source voice platform Resonate, i am preparing a script, to clone our main backend architecture on appwrite self hosted on the contributors local host. The script needs to be as automated as possible but
appwrite projects create --projectId resonate --name Resonate --teamId 666ce18b003caf6274b6
The command to create a project requires the teamId (organisation iD) as an argument but as there is no means for me to create an organisation the from CLI I would have to take this teamId from the contributor as an input. If there was a command to create an organisation from the CLI hence providing the id of it as the teamId argument in the create project command this would entirely automate my script without the need of any input from the contributor
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: