Git/yunohost-gitea_ynh
1
0
Fork 0
mirror of https://framagit.org/YunoHost-Apps/gitea_ynh.git synced 2025-09-02 18:18:31 +02:00
Code Issues Packages Projects Releases Wiki Activity

Add support to sync yunohost group to organisation teams

Browse Source
This commit is contained in:
Josué Tille
2024-02-05 22:45:24 +01:00
parent 8fb1399ab2
commit 5f7b535237
4 changed files with 24 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
doc/ADMIN.md
View File

@ -46,7 +46,7 @@ client_max_body_size 200M;
Don't forget to restart Gitea:
```bash
sudo systemctl restart __APP__.service`.
sudo systemctl restart __APP__.service.
```
> These settings are restored to the default configuration when updating Gitea. Remember to restore your configuration after all updates.
@ -65,6 +65,20 @@ If you want to bypass the safety backup before upgrading, run:
yunohost app upgrade --no-safety-backup __APP__
```
## Group management
Gitea support Yunohost group sync with Gitea Organisation Team.
As the organisation link to the group depends of the instance this should be configured by the admin on the gitea configuration interface in `DOMAIN/GITEA_PATH/admin/auths/1`.
Normally the admin just need to set the correct value of the `LDAP Group Team Map` parameter with something like this:
```json
{"cn=GROUPE_A_YNH,ou=groups,dc=yunohost,dc=org": {"gitea_organisation": ["gitea_team_A"]},
"cn=GROUPE_B_YNH,ou=groups,dc=yunohost,dc=org": {"gitea_organisation": ["gitea_team_B"]}}
```
By this all members of the Yunohost groupe `GROUPE_A_YNH` will be member of the gitea team `gitea_team_A` of the organisation `gitea_organisation`.
**Note all others parameter are managed by the Yunohost package and should not be changed.**
## Backup
This application now uses the core-only feature of the backup. To keep the integrity of the data and to have a better guarantee of the restoration it is recommended to proceed as follows: