Merge branch 'YunoHost:master' into master

pages/02.administer/15.admin_guide/25.domains/01.certificate/certificate.de.md

@@ -55,13 +55,13 @@ SSH-Zugang auf Ihrem Server herstellen.
 So können Sie den aktuellen Status des digitalen Zertifikats überprüfen
 
 ```bash
-yunohost domain cert-status Ihre.domain.tld
+yunohost domain cert status Ihre.domain.tld
 ```
 
 Dann Let's Encrypt-Zertifikat installieren
 
 ```bash
-yunohost domain cert-install Ihre.domain.tld
+yunohost domain cert install Ihre.domain.tld
 ```
 
 Ergebnis sollte so aussehen :
@@ -82,7 +82,7 @@ Wenn das Zertifikat aufgrund einer schlechten Handhabung nicht funktionsfähig i
 ein selbst-signiertes Zertifikat zu regenerieren :
 
 ```bash
-yunohost domain cert-install Ihre.domain.tld --self-signed --force
+yunohost domain cert install Ihre.domain.tld --self-signed --force
 ```
 
 Trotz einer sorgfältigen Überprüfung der DNS-Konfiguration und auch von außen
@@ -90,4 +90,4 @@ die Möglichkeit mit HTTP-Modus Zugriff auf den Webserver besteht, kann YunoHost
 manschmal die Einstellungen verweigern. In diesem Fall ist es notwendig :
 
 - die Parameter `127.0.0.1 Ihre.domain.tld` auf der Datei `/etc/hosts` des Webserver hinzufügen.
-Wenn es immer noch nicht funktionsfähig ist, also die Überprüfungen deaktivieren mit `--no-checks` nach dem Befehl `cert-install`.
+Wenn es immer noch nicht funktionsfähig ist, also die Überprüfungen deaktivieren mit `--no-checks` nach dem Befehl `cert install`.

pages/02.administer/15.admin_guide/25.domains/01.certificate/certificate.es.md

@@ -50,13 +50,13 @@ Conectate en tu servidor en SSH.
 Puedes comprobar el estatus corriente de tu certificado vía
 
 ```bash
-yunohost domain cert-status tu.dominio.tld
+yunohost domain cert status tu.dominio.tld
 ```
 
 Instala el certificado Let's Encrypt vía
 
 ```bash
-yunohost domain cert-install tu.dominio.tld
+yunohost domain cert install tu.dominio.tld
 ```
 
 Este comando debe devolverte :
@@ -73,10 +73,10 @@ Una vez que la instalación está terminada, puedes dirigirte a tu dominio vía
 Si, después de una manipulación incorrecta, un certificado se encuentra en una mala situación (e.g. pérdida del certificado o imposibilidad de leerlo), es posible regenerar un certificado autofirmado :
 
 ```bash
-yunohost domain cert-install tu.dominio.tld --self-signed --force
+yunohost domain cert install tu.dominio.tld --self-signed --force
 ```
 
 Si YunoHost te dice que tu dominio está mal configurado mientras que has verificado tu configuración DNS y que tienes acceso a tu servidor en HTTP desde afuera, puedes intentar :
 
 - de añadir una línea `127.0.0.1 tu.dominio.tld` al archivo `/etc/hosts` en tu servidor ;
-- si la instalación todavía no funciona, desactiva las verificaciones añadiendo `--no-checks` al comando `cert-install`.
+- si la instalación todavía no funciona, desactiva las verificaciones añadiendo `--no-checks` al comando `cert install`.

pages/02.administer/15.admin_guide/25.domains/01.certificate/certificate.fr.md

@@ -59,13 +59,13 @@ Connectez-vous sur votre serveur en SSH.
 Vous pouvez vérifier le statut actuel de votre certificat via :
 
 ```bash
-yunohost domain cert-status votre.domaine.tld
+yunohost domain cert status votre.domaine.tld
 ```
 
 Installez le certificat Let's Encrypt via :
 
 ```bash
-yunohost domain cert-install votre.domaine.tld
+yunohost domain cert install votre.domaine.tld
 ```
 
 Cette commande doit retourner :
@@ -88,7 +88,7 @@ certificat), il est possible de repartir sur des bases propres en regénérant u
 certificat auto-signé :
 
 ```bash
-yunohost domain cert-install votre.domaine.tld --self-signed --force
+yunohost domain cert install votre.domaine.tld --self-signed --force
 ```
 
 Si YunoHost trouve que votre domaine est mal configuré quand bien même vous
@@ -96,4 +96,4 @@ avez bien vérifié votre configuration DNS et avez bien accès à votre serveur
 HTTP depuis l'extérieur, vous pouvez tenter :
 
 - d'ajouter une ligne `127.0.0.1 votre.domaine.tld` au fichier `/etc/hosts` sur votre serveur ;
-- si l'installation ne fonctionne toujours pas, de désactiver les vérifications en ajoutant `--no-checks` à la commande `cert-install`.
+- si l'installation ne fonctionne toujours pas, de désactiver les vérifications en ajoutant `--no-checks` à la commande `cert install`.

pages/02.administer/15.admin_guide/25.domains/01.certificate/certificate.it.md

@@ -57,13 +57,13 @@ Collegatevi al server con SSH.
 Potete controllare lo stato del certificato in uso con il comando:
 
 ```bash
-yunohost domain cert-status your.domain.tld
+yunohost domain cert status your.domain.tld
 ```
 
 Installate il certificato Let's Encrypt con il comando:
 
 ```bash
-yunohost domain cert-install your.domain.tld
+yunohost domain cert install your.domain.tld
 ```
 
 Che dovrebbe dare come risultato:
@@ -83,10 +83,10 @@ Una volta installato il certificato potete verificarne il corretto funzionamento
 Se il vostro certificato risultasse non funzionante a causa di qualche errore (ad esempio lo avete perso oppure non siete in grado di leggere i file) potete ripulire la situazione rigenerando un certificato autofirmato con questo comando:
 
 ```bash
-yunohost domain cert-install your.domain.tld --self-signed --force
+yunohost domain cert install your.domain.tld --self-signed --force
 ```
 
 Se YunoHost pensa che il vostro dominio non è configurato correttamente nonstante abbiate controllato la configurazione del DNS e riuscite a collegarvi in HTTP al vostro server anche dall'esterno della rete locale allora potete:
 
 - aggiungere una linea `127.0.0.1 vostrodominio.tld` nel file `/etc/hosts` sul vostro server;
-- se nonostante questo l'installazione del certificato dovesse ancora fallire potete disabilitare il controllo con l'opzione `--no-checks` dopo il comando `cert-install`.
+- se nonostante questo l'installazione del certificato dovesse ancora fallire potete disabilitare il controllo con l'opzione `--no-checks` dopo il comando `cert install`.

pages/02.administer/15.admin_guide/25.domains/01.certificate/certificate.md

@@ -50,13 +50,13 @@ Connect to your server through SSH.
 You can check the status of your current certificate with:
 
 ```bash
-yunohost domain cert-status your.domain.tld
+yunohost domain cert status your.domain.tld
 ```
 
 Install a Let's Encrypt certificate with
 
 ```bash
-yunohost domain cert-install your.domain.tld
+yunohost domain cert install your.domain.tld
 ```
 
 This should return :
@@ -76,10 +76,10 @@ Once this is done, you can check that the certificate is live via your browser b
 If due to some bad tweaking, your certificate ends up in a bad state (e.g. lost the certificate or unable to read the files), you should be able to clean the situation by regenerating a self-signed certificate:
 
 ```bash
-yunohost domain cert-install your.domain.tld --self-signed --force
+yunohost domain cert install your.domain.tld --self-signed --force
 ```
 
 If YunoHost thinks that your domain is badly configured despite the fact that you checked the DNS configuration and you have access in HTTP to your server from outside your local network, then you can:
 
 - add a line `127.0.0.1 your.domain.tld` to the file `/etc/hosts` on your server;
-- if the certificate installation still doesn't work, you can disable the checks with `--no-checks` after the `cert-install` command.
+- if the certificate installation still doesn't work, you can disable the checks with `--no-checks` after the `cert install` command.

pages/06.contribute/10.packaging_apps/10.manifest/10.appresources/packaging_app_manifest_resources.md

@@ -1,5 +1,5 @@
 ---
-title: App manifest resources
+title: App resources
 template: docs
 taxonomy:
     category: docs
@@ -7,7 +7,7 @@ routes:
   default: '/packaging_apps_resources'
 ---
 
-Doc auto-generated by [this script](https://github.com/YunoHost/yunohost/blob/7d0d82ae016ae3e7cdb06423b67678d7f7a5d9ca/doc/generate_resource_doc.py) on 11/04/2024 (YunoHost version 11.2.11.2)
+Doc auto-generated by [this script](https://github.com/YunoHost/yunohost/blob/d5e054fe80002862bd5966d61b20e9fafcf0578e/doc/generate_resource_doc.py) on 20/05/2024 (YunoHost version 11.2.12)
 
 
 ---
@@ -342,3 +342,4 @@ Provision a system user to be used by the app. The username is exactly equal to
 
 ### Deprovision
 - deletes the user and group
+

pages/06.contribute/10.packaging_apps/60.advanced/60.advanced_packagers/advanced_packagers.md

@@ -58,7 +58,7 @@ With that you will be able to install two apps on the same YunoHost first one at
 
 When your infrastructure is up and ready, you will have to do snapshots of each VMs/LXCs. Doing that, you will be able to revert back to an happy and healthy YunoHost after doing install/backup/restore/upgrade of and app...
 
-Don't forget to regularly upgrade your YunoHosts VMs/LXCs to the last release doing: revert back to last happy/healthy YunoHost snapshot and doing `yunohost domain cert-renew --no-check && yunohost tools update && yunohost tools upgrade --apps && yunohost tools upgrade --system && apt autoremove`. Take a snapshot after that successfull full upgrade. And after some testings or one week later, remove old snapshot. PS: that can be automated...
+Don't forget to regularly upgrade your YunoHosts VMs/LXCs to the last release doing: revert back to last happy/healthy YunoHost snapshot and doing `yunohost domain cert renew --no-check && yunohost tools update && yunohost tools upgrade --apps && yunohost tools upgrade --system && apt autoremove`. Take a snapshot after that successfull full upgrade. And after some testings or one week later, remove old snapshot. PS: that can be automated...
 
 Example of a script to upgrade a master VirtualBox VM