You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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...
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.
The text was updated successfully, but these errors were encountered: