Content
View differences
Updated by Marc Alcobé about 3 years ago
* Research the group folder feature of Nextcloud, its usage and limitations
On installation or migration the following logic should be applied
* Check if the installation is "blank" so that we can safely create the missing user, group and group folder.
* Also check if the installation was already complete as it could be that user, group and group folder already correctly exist from an earlier installation. If there is everything in place and correctly setup then reuse the existing ones. The combination of group folder, group user and user is so unique that I believe that it is safe to assume that these objects are there from an earlier installation.
* If any of the objects exists, but the setup appears incomplete, don't proceed in creating them. Instead show an error message explaining that there cannot be a user, group and group folder with the name "OpenProject". The user should either fix the setup manually if she wants to reuse them or rename them.
* In case the it is "blank" then
* Create the group "OpenProject"
* Create the user "OpenProject" and make it group admin of "OpenProject" so that it can manage its group memberships.
* Create the group folder "OpenProject" and bind it to group "OpenProject". Make the user "OpenProject" have "advanced permissions" to manage access control lists for files and folders.
* Generate an app password for the "OpenProject" user and show it to the Nextcloud admin.
* In order to allow this automation, an An extra step of both Nextcloud and OpenProject setup will be added in order to select if copy the users want the "Automatically managed folders" active or not. (see visuals)
* In case the app system user selects to use the "Automatic managed folders" a new step (number 5) will be added to Nextcloud in order to see the application password the admin need from OpenProject to copy to OpenProject.
* As the setup steps are now 4 or 5 the action on the button of the step 3 also changes. Nextcloud. (see visuals)
* The user The usr should be able to deactivate the "Automatically managed folders" or reset this password once all the process is completed. (see visual)
## Visuals
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/52569/content"><img src="/api/v3/attachments/51938/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/52574/content"><img src="/api/v3/attachments/51831/content">
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/52573/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/52575/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/52570/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/52572/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/52571/content"> src="/api/v3/attachments/51937/content">
On installation or migration the following logic should be applied
* Check if the installation is "blank" so that we can safely create the missing user, group and group folder.
* Also check if the installation was already complete as it could be that user, group and group folder already correctly exist from an earlier installation. If there is everything in place and correctly setup then reuse the existing ones. The combination of group folder, group user and user is so unique that I believe that it is safe to assume that these objects are there from an earlier installation.
* If any of the objects exists, but the setup appears incomplete, don't proceed in creating them. Instead show an error message explaining that there cannot be a user, group and group folder with the name "OpenProject". The user should either fix the setup manually if she wants to reuse them or rename them.
* In case the it is "blank" then
* Create the group "OpenProject"
* Create the user "OpenProject" and make it group admin of "OpenProject" so that it can manage its group memberships.
* Create the group folder "OpenProject" and bind it to group "OpenProject". Make the user "OpenProject" have "advanced permissions" to manage access control lists for files and folders.
* Generate an app password for the "OpenProject" user and show it to the Nextcloud admin.
* In order to allow this automation, an
* In case the
* As the setup steps are now 4 or 5 the action on the button of the step 3 also changes.
* The user
## Visuals
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/52569/content"><img
<img