-
-
Notifications
You must be signed in to change notification settings - Fork 259
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
Feature Request: User Permission system #279
Comments
First of all, it's very pleasant to read this, I'm glad that Cloud Commander, can be useful :).
There is a very good idea, a lot of people want this feature, and a good place to start with is using configManager. Could you please try to use For a long time |
Sounds good! I'll try out the middleware and see how we can tackle this. I'm a little confused on the idea of using cloud commander - a stand-alone file manager - as middleware. Is it so people can add a file manager to their applications or to build their own filemanager entirely? |
Both things are possible :) |
@SimplyBallistic do you have any progress on this :)? |
I got a chance to explore the codebase and set up my environment but other than that, haven't dove too deep into development. I have a pretty busy April but afterwards I'll likely find time to give this a good shot 🙌🏾 |
Hey @coderaiser, great job with cloudcmd!
I've been using the program for a few years now and it's a remarkable tool for complex file operations on my headless server. Thank you for your incredible work on the project ❤️
Now, I've arrived at this special use case where I want to share access to my server with others so they can add question JSON files for this full-stack education program I'm writing. My server will host the test environment and the idea of them just simply logging on and adding questions to rapidly test sounds like the kind of simplicity I could use right now.
It got me thinking, a user/permission system for cloudcmd would be amazing, allowing people to share access to their server without the worry it'll be on fire the next day.
These are the permissions I've thought of so far:
Possible extension of this feature:
Of course, this feature is a big ask. However, if you think it's worth the time, I'd be happy to help make it a reality. Just a quick idea of the stack, prerequisites and where the foundations are in the code and I'll be on it 🙌
The text was updated successfully, but these errors were encountered: