Skip to content
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

[Suggestion] Share databases with DB4S 'admin' #198

Open
chrisjlocke opened this issue Apr 30, 2023 · 4 comments
Open

[Suggestion] Share databases with DB4S 'admin' #198

chrisjlocke opened this issue Apr 30, 2023 · 4 comments

Comments

@chrisjlocke
Copy link
Member

chrisjlocke commented Apr 30, 2023

How easy would it be to allow databases to be shared with DB4S admin?
My thought process was for someone posting a DB4S issue to upload their database to DBHub.io, but they're going to make it private. They're not going to then want to add justinclift, chrisjlocke, mkleusberg, lucydo, scottfurry, et al so they can view it. However, in the upload process (if a flag of 'admin' was set in the URL?) it would then add those users in automatically. At some point that list may have to be edited (if we get a new support person, etc) but that's a minor fiddle. Actually, I've another brain fart related to that. There could be another 'settings' database in the background which could be edited like any other database, so would just need an API call to edit.

@chrisjlocke
Copy link
Member Author

chrisjlocke commented Apr 30, 2023

Semi linked to this is the idea of groups I guess. So a bunch of users is a group, 'some' members of the group are admin to allow adding other users to the group .. on upload, you can add an option to the URL (or via API?) so its gets read-only access to that group. Or write-access. The above 'easy part 1' is quicker to implement though. I'm thinking the more we advertise DBHub.io to share databases, the more familiar it'll be...

@justinclift
Copy link
Member

The concept of "user uploads database, to share with admin(s)" sounds reasonable.

The implementation would need a bit of thinking about.

You're right, it does indeed touch upon group/team membership, which is on our ToDo list though we haven't really thought it through yet. 😄

@chrisjlocke
Copy link
Member Author

The implementation would need a bit of thinking about

Can't we just implement it then change it later? ;)

@justinclift
Copy link
Member

Not tonight. 😉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants