mirror of
https://github.com/YunoHost/doc.git
synced 2024-09-03 20:06:26 +02:00
Fix typos
This commit is contained in:
Éric Gaspar
parent
075849f174
commit
8c98a9c34f
6 changed files with 14 additions and 18 deletions
|
|
@ -100,16 +100,16 @@ This section contains questions that should be asked to the admin prior to start
|
|||
```toml
|
||||
[install]
|
||||
[install.domain]
|
||||
# this is a generic question - ask strings are automatically handled by Yunohost's core
|
||||
# this is a generic question - ask strings are automatically handled by YunoHost's core
|
||||
type = "domain"
|
||||
|
||||
[install.path]
|
||||
# this is a generic question - ask strings are automatically handled by Yunohost's core
|
||||
# this is a generic question - ask strings are automatically handled by YunoHost's core
|
||||
type = "path"
|
||||
default = "/helloworld"
|
||||
|
||||
[install.init_main_permission]
|
||||
# this is a generic question - ask strings are automatically handled by Yunohost's core
|
||||
# this is a generic question - ask strings are automatically handled by YunoHost's core
|
||||
type = "group"
|
||||
default = "visitors"
|
||||
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ The SSO system is handled by [SSOwat](https://github.com/YunoHost/ssowat) and al
|
|||
|
||||
LDAP is a de-facto standard when it comes to sharing a common user account database between multiple applications, hence its use in the context of YunoHost.
|
||||
|
||||
However, each app does implement LDAP support in its own specific way (or doesn't), and needs to be provided with parameters to actually talk to YunoHost's LDAP database, usually via its config file. It is advise to look for real-life example of apps implementing these (such as Nextcloud, Wekan, ...) but you will usually need to provide:
|
||||
However, each app does implement LDAP support in its own specific way (or doesn't), and needs to be provided with parameters to actually talk to YunoHost's LDAP database, usually via its config file. It is advise to look for real-life example of apps implementing these (such as Nextcloud, Wekan...) but you will usually need to provide:
|
||||
|
||||
- LDAP host: `localhost` / `127.0.0.1`
|
||||
- LDAP port: `389`
|
||||
|
|
@ -32,11 +32,11 @@ However, each app does implement LDAP support in its own specific way (or doesn'
|
|||
- Display name attribute: `displayname`
|
||||
- Email attribute: `mail`
|
||||
|
||||
TODO/FIXME : moar explanations ? What is missing ?
|
||||
TODO/FIXME: moar explanations? What is missing?
|
||||
|
||||
## SSO integration
|
||||
|
||||
Internally, SSOwat will on-the-fly inject [HTTP Basic Auth Headers](https://en.wikipedia.org/wiki/Basic_access_authentication) like `Authorization: Basic <base64credentials>`. Some applications may include Basic Auth support out of the box ... PHP apps do often require this line in the NGINX config:
|
||||
Internally, SSOwat will on-the-fly inject [HTTP Basic Auth Headers](https://en.wikipedia.org/wiki/Basic_access_authentication) like `Authorization: Basic <base64credentials>`. Some applications may include Basic Auth support out of the box... PHP apps do often require this line in the NGINX config:
|
||||
|
||||
```text
|
||||
fastcgi_param REMOTE_USER $remote_user;
|
||||
|
|
@ -45,7 +45,7 @@ fastcgi_param REMOTE_USER $remote_user;
|
|||
`$remote_user` being a special variable in NGINX that maps to the user provided in the HTTP Basic Auth headers. The PHP application will then use the `HTTP_REMOTE_USER` info in its code.
|
||||
|
||||
|
||||
TODO/FIXME : moar explanations of how this is done for non-PHP apps ?
|
||||
TODO/FIXME: moar explanations of how this is done for non-PHP apps?
|
||||
|
||||
|
||||
## Configuring SSOwat permissions for the app
|
||||
|
|
@ -74,8 +74,4 @@ See the page about app resources for the full description of behavior and proper
|
|||
|
||||
A common [known issue](https://github.com/YunoHost/issues/issues/501) is that sometimes, logging out of YunoHost apps will not log people out of every app. This is for example the case for [Nextcloud](https://github.com/YunoHost-Apps/nextcloud_ynh/issues/19), because it uses its own authentication cookies which are not cleared when people log out of YunoHost. This is not trivial to fix.
|
||||
|
||||
Similarly, logging out of the app doesn't necessarily log people from YunoHost entirely (which is more acceptable that clicking Log out and ... not being logged out at all because you're still logged-in on the SSO, hence logged in on the app). Some YunoHost app do integrate custom patches such that the logout process of the app does automatically redirects to `https://domain.tld/yunohost/sso/?action=logout` which logs them out.
|
||||
|
||||
|
||||
|
||||
|
||||
Similarly, logging out of the app doesn't necessarily log people from YunoHost entirely (which is more acceptable that clicking Log out and... not being logged out at all because you're still logged-in on the SSO, hence logged in on the app). Some YunoHost app do integrate custom patches such that the logout process of the app does automatically redirects to `https://domain.tld/yunohost/sso/?action=logout` which logs them out.
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ taxonomy:
|
|||
routes:
|
||||
default: '/packaging_apps_hooks'
|
||||
---
|
||||
YunoHost comprend un mécanisme de hooks déclenchés lors de nombreuses opérations modifiant le système. Vous pouvez utiliser ce mécanisme afin d'étendre le comportement d'une commande yunohost.
|
||||
YunoHost comprend un mécanisme de hooks déclenchés lors de nombreuses opérations modifiant le système. Vous pouvez utiliser ce mécanisme afin d'étendre le comportement d'une commande YunoHost.
|
||||
|
||||
Le cas le plus évident est l'ajout d'un utilisateur. Si vous aviez un hook `post_user_create`, ce hook sera déclenché dès qu'un utilisateur sera ajouté.
|
||||
|
||||
|
|
@ -24,7 +24,7 @@ nano /etc/yunohost/hooks.d/post_user_create/05-add-user-to-samba
|
|||
```
|
||||
|
||||
## Comment ajouter un hook dans un paquetage d'application
|
||||
Si vous empaquetez une application, vous ne devez pas mettre vous-même le hook dans `/etc/yunohost/hooks.d mais vous devez créer un répertoire hooks à la racine de votre paquet.
|
||||
Si vous empaquetez une application, vous ne devez pas mettre vous-même le hook dans `/etc/yunohost/hooks.d` mais vous devez créer un répertoire hooks à la racine de votre paquet.
|
||||
```
|
||||
.
|
||||
├─── conf
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ routes:
|
|||
default: '/packaging_apps_hooks'
|
||||
---
|
||||
|
||||
YunoHost includes a hook mechanism triggered on a lot of operation changing the system. You can use this mechanism in order to extend the behaviour of a yunohost command.
|
||||
YunoHost includes a hook mechanism triggered on a lot of operation changing the system. You can use this mechanism in order to extend the behaviour of a YunoHost command.
|
||||
|
||||
The most obvious case is adding a user. If you had a `post_user_create` hook, this hook will be triggered as soon as a user is added.
|
||||
|
||||
|
|
|
|||
|
|
@ -201,5 +201,5 @@ With advanced packaging comes [CI_package_check](https://github.com/YunoHost/CI_
|
|||
|
||||
When you do several things at the same time, sometimes you don't remember what is the next step for this or that app.
|
||||
A good tool to keep your TODO list organized is to use a kaban like apps:
|
||||
- [kanboard](https://github.com/YunoHost-Apps/kanboard_ynh)
|
||||
- [wekan](https://github.com/YunoHost-Apps/wekan_ynh)
|
||||
- [Kanboard](https://github.com/YunoHost-Apps/kanboard_ynh)
|
||||
- [Wekan](https://github.com/YunoHost-Apps/wekan_ynh)
|
||||
|
|
|
|||
|
|
@ -108,6 +108,6 @@ Il contient essentiellement :
|
|||
- Pour une correction de bug : `fix-REDMINETICKET-description-correctif`
|
||||
- `ISSUENUMBER` est optionnel et correspond au numéro du ticket sur le bug tracker
|
||||
|
||||
- Une fois prêt, ouvrez une Pull Request (PR) sur Github. De préférence, inclure `[fix]` ou `[enh]` au début du titre de la PR.
|
||||
- Une fois prêt, ouvrez une Pull Request (PR) sur GitHub. De préférence, inclure `[fix]` ou `[enh]` au début du titre de la PR.
|
||||
|
||||
- Après relecture, test et validation par les autres contributeurs, votre branche sera mergée dans `unstable` !
|
||||
|
|
|
|||
Loading…
Reference in a new issue