Replies: 4 comments
-
|
Hey @monatis , please let me know if this help you: If not, please provide us with more information about your exact use case and needs. |
Beta Was this translation helpful? Give feedback.
-
|
hi @eldadfux, yes this serves the purpose for now, but I would suggest a settings screen on the console similar to self-hosted Gitlab when Appwrite hits stable V1.0. This would make it flawless to manage the whitelist in the long run. For this purpose, the first signed-up user might be deemed to be the root user. |
Beta Was this translation helpful? Give feedback.
-
|
@monatis Sounds awesome, I will add it to our roadmap for v1.0.0. Would be great if you could bring more feedback on the root user and what features are needed for the global admin dashboard. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @eldadfux, thanks a lot for the positive response and adding it to your v1.0 roadmap. In my opinion and in the ideal world, the root user might be able to:
Also, a sudo mode might be implemented, so that the root user need to enter their password again to make root-level changes, etc. I think that these features will make Appwrite a perfect fit for teams of any size. I hope to contribute with possible commits after I'm done with the ongoing busy period in my projects. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I had the chance to test Appwrite, thanks for the great project.
One thing that I can't find is, there are no installation-wide settings on the console. For example, it would be great if we could limit new signups after the first one and control who can create projects on that particular Appwrite installation.
Beta Was this translation helpful? Give feedback.
All reactions