From 6d4b2d225d591c848b410733399b95b70593d859 Mon Sep 17 00:00:00 2001 From: OniriCorpe Date: Sat, 2 Mar 2024 07:07:57 +0100 Subject: [PATCH] various manual fixes --- orphaned/default.es.md | 2 +- orphaned/default.fr.md | 2 +- orphaned/default.it.md | 2 +- orphaned/default.md | 2 +- orphaned/news.md | 2 +- orphaned/registrar.fr.md | 10 +++---- orphaned/registrar.md | 10 +++---- .../how_to_host_yourself.ru.md | 1 - .../15.isp_box_config/isp_box_config.de.md | 8 +++--- .../15.isp_box_config/isp_box_config.es.md | 8 +++--- .../15.isp_box_config/isp_box_config.fr.md | 8 +++--- .../15.isp_box_config/isp_box_config.md | 8 +++--- .../25.installing_debian/installing_debian.md | 4 +-- pages/02.administer/10.install/install.de.md | 27 ++++++++++--------- pages/02.administer/10.install/install.fr.md | 15 ++++++----- pages/02.administer/10.install/install.md | 27 ++++++++++--------- pages/02.administer/10.install/install.ru.md | 22 +++++++-------- .../05.guidelines/guidelines.de.md | 2 +- .../05.guidelines/guidelines.fr.md | 2 +- .../05.guidelines/guidelines.it.md | 2 +- .../05.guidelines/guidelines.md | 2 +- .../15.admin_guide/10.admin/admin.de.md | 2 +- .../15.admin_guide/10.admin/admin.es.md | 2 +- .../15.admin_guide/10.admin/admin.fr.md | 2 +- .../15.admin_guide/10.admin/admin.it.md | 2 +- .../15.admin_guide/10.admin/admin.md | 2 +- .../15.command_line/command_line.de.md | 6 ++--- .../15.command_line/command_line.es.md | 2 +- .../15.admin_guide/30.apps/apps.fr.md | 2 +- .../15.admin_guide/30.apps/apps.it.md | 2 +- .../15.admin_guide/30.apps/apps.md | 2 +- .../stretch_buster_migration.md | 2 +- .../buster_bullseye_migration.md | 2 +- .../20.backups/05.evaluate/evaluate.md | 6 ++--- .../custom_backup_methods.it.md | 1 - .../custom_backup_methods.md | 1 - .../03.dns_subdomains/dns_subdomains.fr.md | 2 +- .../03.dns_subdomains/dns_subdomains.md | 2 +- .../external_storage.fr.md | 4 +-- .../external_storage.it.md | 4 +-- .../25.external_storage/external_storage.md | 12 ++++----- .../40.tor/torhiddenservice.fr.md | 2 +- .../40.tor/torhiddenservice.it.md | 2 +- .../45.tutorials/40.tor/torhiddenservice.md | 2 +- .../certificate_custom.fr.md | 12 ++++----- .../certificate_custom.md | 12 ++++----- .../15.noaccess/noaccess.fr.md | 6 ++--- .../15.noaccess/noaccess.it.md | 2 +- .../15.noaccess/noaccess.md | 2 +- .../50.troubleshooting/20.ipv6/ipv6.fr.md | 2 +- .../50.troubleshooting/20.ipv6/ipv6.it.md | 2 +- .../50.troubleshooting/20.ipv6/ipv6.md | 2 +- .../25.unblacklisting/blacklist_forms.md | 2 +- .../02.administer/55.providers/10.isp/isp.md | 1 + .../10.isp/orange/isp_orange.fr.md | 2 +- .../15.vpn/01.vpn/vpn_advantage.es.md | 12 ++++----- .../60.extend/30.api/admin_api.md | 10 +++---- .../email_configure_client.de.md | 6 ++--- .../email_configure_client.fr.md | 6 ++--- .../email_configure_client.it.md | 8 +++--- .../05.emailclients/email_configure_client.md | 6 ++--- pages/05.community/15.help/help.fr.md | 2 +- pages/05.community/15.help/help.md | 4 +-- pages/05.community/20.faq/faq.fr.md | 2 +- pages/05.community/20.faq/faq.it.md | 2 +- pages/05.community/20.faq/faq.md | 2 +- .../35.project_budget/project_budget.fr.md | 4 +-- .../35.project_budget/project_budget.md | 4 +-- .../03.git/doc_use_git.fr.md | 7 +++-- .../03.git/doc_use_git.md | 6 ++--- .../write_documentation.de.md | 2 +- .../10.packaging_apps/40.testing/testing.md | 2 +- .../11.helpers/packaging_apps_helpers.md | 6 ++--- .../packaging_apps_resources.md | 2 +- pages/06.contribute/15.dev/dev.fr.md | 12 ++++----- pages/06.contribute/15.dev/dev.md | 4 +-- 76 files changed, 193 insertions(+), 193 deletions(-) diff --git a/orphaned/default.es.md b/orphaned/default.es.md index b1021d46..44faf041 100644 --- a/orphaned/default.es.md +++ b/orphaned/default.es.md @@ -4,7 +4,7 @@ Esta página todavía no existe, puedes editarla tecleando `````` en tu t **Nota :** Necesitarás una dirección email para validar tu propuesta. -### Sintaxis +## Sintaxis Esta página utiliza la sintaxis Markdown, refiérete a la documentación para más informaciones : diff --git a/orphaned/default.fr.md b/orphaned/default.fr.md index 6bcd506e..1deba1e8 100644 --- a/orphaned/default.fr.md +++ b/orphaned/default.fr.md @@ -4,7 +4,7 @@ Cette page n’existe pas encore, vous pouvez l’éditer en appuyant sur la tou **Note :** Vous aurez besoin d'une adresse email pour valider votre proposition. -### Syntaxe +## Syntaxe Cette page utilise la syntaxe Markdown, veuillez vous référer à la documentation pour plus d’informations : diff --git a/orphaned/default.it.md b/orphaned/default.it.md index a22f6775..54b9c340 100644 --- a/orphaned/default.it.md +++ b/orphaned/default.it.md @@ -4,7 +4,7 @@ Questa pagina non è ancora stata creata, puoi modificarla premendo `````` **Nota:** Devi fornire un indirizzo email per confermare le tue modifiche. -### Sintassi +## Sintassi Questa pagina usa la sintassi markdown, per favore fai riferimento alla documentazione per ulteriori informazioni: diff --git a/orphaned/default.md b/orphaned/default.md index 0d7b1940..c0339711 100644 --- a/orphaned/default.md +++ b/orphaned/default.md @@ -4,7 +4,7 @@ This page is not created yet, you can edit it by pressing `````` on your ke **Note:** You will need to provide an email address to validate your submission. -### Syntax +## Syntax This page use the markdown syntax, please refer to the documentation for further informations: diff --git a/orphaned/news.md b/orphaned/news.md index 57db71c2..a3975fc3 100644 --- a/orphaned/news.md +++ b/orphaned/news.md @@ -33,7 +33,7 @@ $(document).ready(function() { $(data).find("item").each(function(_, item) { var description = $(item).find("description"); // yes this is a NIGHTMARE - var blockquote_content = $("
" + description[0].textContent + "
").find["blockquote"](0).innerHTML + var blockquote_content = $("
" + description[0].textContent + "
").find("blockquote")[0].innerHTML // blockquote_content = blockquote_content.replace("(HTTP), 443 (HTTPS) -- [SSH](/ssh): 22 -- [XMPP](/XMPP): 5222 (clients), 5269 (servers) -- [Email](/email): 25, 587 (SMTP), 993 (IMAP) +- Web: `80` (HTTP), `443` (HTTPS) +- [SSH](/ssh): `22` +- [XMPP](/XMPP): `5222` (clients), `5269` (servers) +- [Email](/email): `25`, `587` (SMTP), `993` (IMAP) Wenn Sie sowohl ein Modem als auch einen Router verwenden, dann müssen Sie Folgendes tun: diff --git a/pages/02.administer/10.install/15.isp_box_config/isp_box_config.es.md b/pages/02.administer/10.install/15.isp_box_config/isp_box_config.es.md index 3ca194da..cef0d5e6 100644 --- a/pages/02.administer/10.install/15.isp_box_config/isp_box_config.es.md +++ b/pages/02.administer/10.install/15.isp_box_config/isp_box_config.es.md @@ -44,10 +44,10 @@ En la interfaz de administración de tu router/caja/box, tienes que encontrar un Luego tienes que redirigir cada uno de los puertos listados a continuación hacia la IP local de tu router para que los varios servicios de YunoHost funcionen. Para cada uno de ellos, una redirección 'TCP' es necesaria. En algunas interfaces, tal vez encontrarás referencias a un puerto 'externo' y un puerto 'interno' : en nuestro caso, se trata del mismo número de puerto, que sea interno o externo. -- Web: 80 (HTTP), 443 (HTTPS) -- [SSH](/ssh): 22 -- [XMPP](/XMPP): 5222 (clients), 5269 (servers) -- [Email](/email): 25, 587 (SMTP), 993 (IMAP) +- Web: `80` (HTTP), `443` (HTTPS) +- [SSH](/ssh): `22` +- [XMPP](/XMPP): `5222` (clients), `5269` (servers) +- [Email](/email): `25`, `587` (SMTP), `993` (IMAP) ! [fa=exclamation-triangle /] Algunos proveedores de acceso a Internet bloquean el puerto 25 (mail SMTP) por defecto para luchar con el spam. Otros (más escasos) no permiten utilizar libremente los puertos 80/443. Dependiendo de tu proveedor, puede ser posible de abrir estos puertos en la interfaz... Ver [esta página](/isp) por más informaciones. diff --git a/pages/02.administer/10.install/15.isp_box_config/isp_box_config.fr.md b/pages/02.administer/10.install/15.isp_box_config/isp_box_config.fr.md index 61d7c75c..68bc6b00 100644 --- a/pages/02.administer/10.install/15.isp_box_config/isp_box_config.fr.md +++ b/pages/02.administer/10.install/15.isp_box_config/isp_box_config.fr.md @@ -45,10 +45,10 @@ nom diffère suivant le type / marque de la box... Il vous faut ensuite rediriger chacun des ports listés ci-dessous vers l'IP locale de votre serveur pour que les différents services de YunoHost fonctionnent. Pour chacun d'eux, une redirection 'TCP' est nécessaire. Certaines interfaces font référence à un port « externe » et un port « interne » : dans notre cas il s'agit du même. -- Web: 80 (HTTP), 443 (HTTPS) -- [SSH](/ssh): 22 -- [XMPP](/XMPP): 5222 (clients), 5269 (serveurs) -- [Email](/email): 25, 587 (SMTP), 993 (IMAP) +- Web : `80` (HTTP), `443` (HTTPS) +- [SSH](/ssh) : `22` +- [XMPP](/XMPP) : `5222` (clients), `5269` (serveurs) +- [Email](/email) : `25`, `587` (SMTP), `993` (IMAP) ! [fa=exclamation-triangle /] Certains fournisseurs d'accès à Internet bloquent le port 25 (mail SMTP) par défaut pour combattre le spam. D'autres (plus rares) ne permettent pas d'utiliser librement les ports 80/443. En fonction de votre FAI, il peut être possible d'ouvrir ces ports dans l'interface... Voir [cette page](/isp) pour plus d'informations. diff --git a/pages/02.administer/10.install/15.isp_box_config/isp_box_config.md b/pages/02.administer/10.install/15.isp_box_config/isp_box_config.md index 71d627d2..398cb76d 100644 --- a/pages/02.administer/10.install/15.isp_box_config/isp_box_config.md +++ b/pages/02.administer/10.install/15.isp_box_config/isp_box_config.md @@ -40,10 +40,10 @@ In your router admin interface, look for something like 'router configuration' o Opening the ports listed below is necessary for the various services available in YunoHost to work. For each of them, the 'TCP' forwarding is needed. Some interfaces refer to 'external' and 'internal' ports : these are the same in our case. -- Web: 80 (HTTP), 443 (HTTPS) -- [SSH](/ssh): 22 -- [XMPP](/XMPP): 5222 (clients), 5269 (servers) -- [Email](/email): 25, 587 (SMTP), 993 (IMAP) +- Web: `80` (HTTP), `443` (HTTPS) +- [SSH](/ssh): `22` +- [XMPP](/XMPP): `5222` (clients), `5269` (servers) +- [Email](/email): `25`, `587` (SMTP), `993` (IMAP) If you use both a modem and a router, then you need to do the following: diff --git a/pages/02.administer/10.install/25.installing_debian/installing_debian.md b/pages/02.administer/10.install/25.installing_debian/installing_debian.md index 75ae05a2..42870842 100644 --- a/pages/02.administer/10.install/25.installing_debian/installing_debian.md +++ b/pages/02.administer/10.install/25.installing_debian/installing_debian.md @@ -27,7 +27,7 @@ This guide won't go into details on how to boot the Debian installer. You can us In general, you can simply follow the instructions on screen and use the suggested defaults. -Debian installer will ask for a **hostname** and a **domain name**. You can use “YunoHost” and “YunoHost.local”. It’s not really important since the YunoHost Installer will overwrite those anyway. +Debian installer will ask for a **hostname** and a **domain name**. You can use `yunohost` and `yunohost.local`. It’s not really important since the YunoHost Installer will overwrite those anyway. Debian will ask for a **root password**. Make sure you pick a **really long and complex** one and save it to your password manager of choice (Bitwarden, Firefox, etc…) or write it somewhere safe. Remember that this is a server that will be available on the internet, making it vulnerable to possible attacks so you should be extra safe here! @@ -36,7 +36,7 @@ The installer will also ask for a **user account** and another password. **Impor When the install asks about where to install and how to **create disk partitions**, select the option to use the whole disk, unless you know what you're doing. - Don’t separate the /home, /var or /tmp partitions. Use the option to “keep all files in one partition”. -- Don’t encrypt any partitions, [as recommended](https://yunohost.org/en/administer/install/hardware:regular#about-encryption)) +- Don’t encrypt any partitions, [as recommended](https://yunohost.org/en/administer/install/hardware:regular#about-encryption) The installer will ask about **mirrors**. Select a country and server close to your location, or use the default options. diff --git a/pages/02.administer/10.install/install.de.md b/pages/02.administer/10.install/install.de.md index 6adc58d2..72104741 100644 --- a/pages/02.administer/10.install/install.de.md +++ b/pages/02.administer/10.install/install.de.md @@ -141,6 +141,7 @@ Wähle die Hardware, auf der du YunoHost installieren willst : ## [fa=list-alt /] Pre-requisites {% if regular %} + - Eine x86-kompatible für YunoHost bestimmte (dedizierte) Hardware: Laptop, Nettop, Netbook, Desktop mit 512MB RAM und 16GB Speicherkapazität (Minimum) {% elseif rpi34 %} - Ein Raspberry Pi 3 oder 4 @@ -230,7 +231,7 @@ sudo apt dist-upgrade Bearbeite `/etc/wsl.conf` und füge den folgenden Code darin ein: -``` +```text [network] generateHosts = false generateResolvConf = false @@ -300,14 +301,14 @@ Rufe `genie -s` immer während des Startes deiner Distro auf. Wie zuvor gesagt, gibt es keine Rollback Möglichkeit. Lass uns deshal deine frische Distro exportieren. In PowerShell: -``` +```bash cd ~ wsl --export YunoHost .\WSL\YunoHost.tar.gz ``` ### Im Falle eines Crash, lösche und stelle die gesamte Distro wieder her -``` +```bash cd ~ wsl --unregister YunoHost wsl --import YunoHost .\WSL\YunoHost .\WSL\YunoHost.tar.gz --version 2 @@ -579,7 +580,7 @@ Wenn du über eine oder mehrere Festplatten zum Speichern von Daten verfügst, k | `/home/yunohost.backup/archives` | YunoHost-Backups, die idealerweise an anderer Stelle als auf den Datenträgern platziert werden, auf denen die Daten verwaltet werden | | `/home/yunohost.app` | Umfangreiche Datenmengen aus YunoHost Apps (nextcloud, matrix...) | | `/home/yunohost.multimedia` | Große Datenmenge, die von mehreren Anwendungen gemeinsam genutzt wird | -| `/var/mail` | User mail +| `/var/mail` | User mail | Wenn du Flexibilität haben möchtest und die Größe von Partitionen nicht (verändern) möchtest, kannst du dich auch dafür entscheiden, auf `/mnt/hdd` zu mounten und dieser [Anleitung zum Mounten aller dieser Ordner mit `mount --bind`](/external_storage) zu folgen. @@ -607,17 +608,17 @@ Raspberry Pi 1 und 0 werden aufgrund von [Kompilierungsproblemen für diese Arch Es ist jedoch möglich, das Image selbst zu reparieren, bevor du die Erstkonfiguration ausführst. -Um das zu erreichen, musst du dich auf deinem Raspberry Pi als Root-Benutzer [über SSH](/ssh) mit dem temporären Passwort „YunoHost“ verbinden: +Um das zu erreichen, musst du dich auf deinem Raspberry Pi als Root-Benutzer [über SSH](/ssh) mit dem temporären Passwort `yunohost` verbinden: -``` +```bash ssh root@yunohost.local ``` -(oder „YunoHost-2.local“ usw., wenn sich mehrere YunoHost-Server in deinem Netzwerk befinden) +(oder `yunohost-2.local` usw., wenn sich mehrere YunoHost-Server in deinem Netzwerk befinden) Führe dann die folgenden Befehle aus, um das Metronomproblem zu umgehen: -``` +```bash mv /usr/bin/metronome{,.bkp} mv /usr/bin/metronomectl{,.bkp} ln -s /usr/bin/true /usr/bin/metronome @@ -626,7 +627,7 @@ ln -s /usr/bin/true /usr/bin/metronomectl Und diesen hier, um das UpnPC-Problem zu umgehen: -``` +```bash sed -i 's/import miniupnpc/#import miniupnpc/g' /usr/lib/moulinette/yunohost/firewall.py ``` @@ -638,7 +639,7 @@ sed -i 's/import miniupnpc/#import miniupnpc/g' /usr/lib/moulinette/yunohost/fir Als nächstes musst du [die lokale IP-Adresse deines Servers finden](/finding_the_local_ip), um dich als Root-Benutzer [über SSH](/ssh) mit dem temporären Passwort `1234` zu verbinden. -``` +```bash ssh root@192.168.x.xxx ``` @@ -722,13 +723,13 @@ Zum Beispiel `ynh.wsl`. Der schwierige Teil besteht darin, diese Domain bei dein Ändere deine `C:\Windows\System32\drivers\etc\hosts` Datei. Du solltest eine Zeile haben, die mit `::1` beginnt. Aktualisiere sie oder füge sie bei Bedarf hinzu, um Folgendes zu erhalten: -``` +```text ::1 ynh.wsl localhost ``` Wenn du Subdomains erstellen möchtest, denk daran, diese auch in der Datei `hosts` hinzuzufügen: -``` +```text ::1 ynh.wsl subdomain.ynh.wsl localhost ``` @@ -768,7 +769,7 @@ Um eine Diagnose auszuführen, gehe im Web Admin auf den Abschnitt "Diagnose". K [/ui-tab] [ui-tab title="In der Kommandozeile"] -``` +```bash yunohost diagnosis run yunohost diagnosis show --issues --human-readable ``` diff --git a/pages/02.administer/10.install/install.fr.md b/pages/02.administer/10.install/install.fr.md index 84758b3f..88a3614f 100644 --- a/pages/02.administer/10.install/install.fr.md +++ b/pages/02.administer/10.install/install.fr.md @@ -131,6 +131,7 @@ Sélectionnez le matériel sur lequel vous souhaitez installer YunoHost : ## [fa=list-alt /] Pré-requis {% if regular %} + - Un matériel compatible x86 dédié à YunoHost : portable, netbook, ordinateur avec 512Mo de RAM et 16Go de capacité de stockage (au moins) ; {% elseif rpi34 %} - Un Raspberry Pi 3 ou 4 ; @@ -338,7 +339,7 @@ Ventoy sera utile si vous n'arrivez pas à démarrer l'image de YunoHost en util 1. Installer [Ventoy](https://www.ventoy.net/) sur la clé USB. Référez-vous aux [instructions d'installation](https://www.ventoy.net/en/doc_start.html). - Cela va créer 2 partition sur la clé USB. -3. En utilisant votre application de fichiers préférée, copiez l'image YunoHost sur la grande partition "Ventoy (pas celle "VTOYEFI") +2. En utilisant votre application de fichiers préférée, copiez l'image YunoHost sur la grande partition "Ventoy (pas celle "VTOYEFI") - N'utilisez pas *Balena Etcher*, USBImager ou `dd` pour faire ça! Insérez cette clé USB dans l'ordinateur et démarrez en utisant celle-ci. Ventoy va apparaitre et lister toutes les images qui sont sur la clé USB. Sélectionnez l'image de YunoHost. Sélectionnez ensuite "GRUB2" comme option de démarrage (ou utilisez n'importe laquelle qui fonctionnera sur votre ordinateur 😉) @@ -480,7 +481,7 @@ Cependant, il est possible de corriger l'image par vous-même avant de lancer la Pour y parvenir, vous devez vous connecter à votre Raspberry Pi en tant que root [via SSH](/ssh) avec le mot de passe temporaire `yunohost`: -``` +```bash ssh root@yunohost.local ``` @@ -488,7 +489,7 @@ ssh root@yunohost.local Ensuite, lancez les commandes suivantes pour contourner le dysfonctionnement de Metronome : -``` +```bash mv /usr/bin/metronome{,.bkp} mv /usr/bin/metronomectl{,.bkp} ln -s /usr/bin/true /usr/bin/metronome @@ -497,7 +498,7 @@ ln -s /usr/bin/true /usr/bin/metronomectl Et celle-ci pour contourner celui de upnpc : -``` +```bash sed -i 's/import miniupnpc/#import miniupnpc/g' /usr/lib/moulinette/yunohost/firewall.py ``` @@ -509,7 +510,7 @@ sed -i 's/import miniupnpc/#import miniupnpc/g' /usr/lib/moulinette/yunohost/fir Ensuite, il vous faut [trouver l'adresse IP locale de votre serveur](/finding_the_local_ip) pour vous connecter en tant que root [via SSH](/ssh) avec le mot de passe temporaire `1234`. -``` +```bash ssh root@192.168.x.xxx ``` @@ -615,7 +616,7 @@ Pour lancer le diagnostic, allez dans l'Administration Web dans la partie Diagno [/ui-tab] [ui-tab title="À partir de la ligne de commande"] -``` +```bash yunohost diagnosis run yunohost diagnosis show --issues --human-readable ``` @@ -639,7 +640,7 @@ Pour plus d'instructions détaillées, ou pour en savoir plus à propos des cert [/ui-tab] [ui-tab title="À partir de la ligne de commande"] -``` +```bash yunohost domain cert install ``` diff --git a/pages/02.administer/10.install/install.md b/pages/02.administer/10.install/install.md index 94d2635d..58c8cefc 100644 --- a/pages/02.administer/10.install/install.md +++ b/pages/02.administer/10.install/install.md @@ -141,6 +141,7 @@ Select the hardware on which you want install YunoHost : ## [fa=list-alt /] Pre-requisites {% if regular %} + - A x86-compatible hardware dedicated to YunoHost: laptop, nettop, netbook, desktop with 512MB RAM and 16GB capacity (at least) {% elseif rpi34 %} - A Raspberry Pi 3 or 4 @@ -230,7 +231,7 @@ sudo apt dist-upgrade Edit `/etc/wsl.conf` and put the following code in it: -``` +```text [network] generateHosts = false generateResolvConf = false @@ -300,14 +301,14 @@ Always call `genie -s` while starting your distro. As said before, there is no rollback capability. So let's export your fresh distro. In PowerShell: -``` +```bash cd ~ wsl --export YunoHost .\WSL\YunoHost.tar.gz ``` ### In case of crash, delete and restore the whole distro -``` +```bash cd ~ wsl --unregister YunoHost wsl --import YunoHost .\WSL\YunoHost .\WSL\YunoHost.tar.gz --version 2 @@ -481,7 +482,7 @@ Ventoy will be useful if you can't sucessfully boot the YunoHost image using the 1. Install [Ventoy](https://www.ventoy.net/) on the USB stick. Refer to the [install instructions](https://www.ventoy.net/en/doc_start.html). - This will create 2 partitions on the stick. -3. Using your favorite file explorer app, copy the YunoHost image file on the big `Ventoy` partition (not "VTOYEFI") +2. Using your favorite file explorer app, copy the YunoHost image file on the big `Ventoy` partition (not "VTOYEFI") - Don't use *Balena Etcher*, USBImager or `dd` for this! Later, when you'll boot the computer using this usb stick, Ventoy will appear and will list the images on the USB stick. Select the YunoHost image, then select GRUB2 launch option (or use whichever works for your computer 😉) @@ -593,7 +594,7 @@ If you have one or more hard drives to store data, you can choose to mount it on | `/home/yunohost.backup/archives` | YunoHost backups to be placed ideally elsewhere than on the disks that manage the data | | `/home/yunohost.app` | Heavy data from YunoHost applications (nextcloud, matrix...) | | `/home/yunohost.multimedia` | Heavy data shared between several applications | -| `/var/mail` | User mail +| `/var/mail` | User mail | If you want flexibility and don't want to (re)size partitions, you can also choose to mount on `/mnt/hdd` and follow this [tutorial to mount all these folders with `mount --bind`](/external_storage). @@ -625,7 +626,7 @@ However, it is possible to fix by yourself the image before to run the initial c To achieve this, you need to connect on your raspberry pi as root user [via SSH](/ssh) with the temporary password `yunohost`: -``` +```bash ssh root@yunohost.local ``` @@ -633,7 +634,7 @@ ssh root@yunohost.local Then run the following commands to work around the metronome issue: -``` +```bash mv /usr/bin/metronome{,.bkp} mv /usr/bin/metronomectl{,.bkp} ln -s /usr/bin/true /usr/bin/metronome @@ -642,7 +643,7 @@ ln -s /usr/bin/true /usr/bin/metronomectl And this one to work around the upnpc issue: -``` +```bash sed -i 's/import miniupnpc/#import miniupnpc/g' /usr/lib/moulinette/yunohost/firewall.py ``` @@ -654,7 +655,7 @@ sed -i 's/import miniupnpc/#import miniupnpc/g' /usr/lib/moulinette/yunohost/fir Next you need to [find the local IP address of your server](/finding_the_local_ip) to connect as root user [via SSH](/ssh) with the temporary password `1234`. -``` +```bash ssh root@192.168.x.xxx ``` @@ -738,13 +739,13 @@ For example, `ynh.wsl`. The tricky part is advertising this domain to your host. Alter your `C:\Windows\System32\drivers\etc\hosts` file. You should have a line starting by `::1`, update it or add it if needed to get: -``` +```text ::1 ynh.wsl localhost ``` If you want to create subdomains, do not forget to add them in the `hosts` file too: -``` +```text ::1 ynh.wsl subdomain.ynh.wsl localhost ``` @@ -784,7 +785,7 @@ To run a diagnosis, go on Web Admin in the Diagnosis section. Click Run initial [/ui-tab] [ui-tab title="From the command line"] -``` +```bash yunohost diagnosis run yunohost diagnosis show --issues --human-readable ``` @@ -810,7 +811,7 @@ Go in Domains > Click on your domain > SSL Certificate [/ui-tab] [ui-tab title="From the command line"] -``` +```bash yunohost domain cert install ``` diff --git a/pages/02.administer/10.install/install.ru.md b/pages/02.administer/10.install/install.ru.md index 64c2e0a3..bc295ecc 100644 --- a/pages/02.administer/10.install/install.ru.md +++ b/pages/02.administer/10.install/install.ru.md @@ -301,14 +301,14 @@ Always call `genie -s` while starting your distro. As said before, there is no rollback capability. So let's export your fresh distro. In PowerShell: -``` +```bash cd ~ wsl --export YunoHost .\WSL\YunoHost.tar.gz ``` ### In case of crash, delete and restore the whole distro -``` +```bash cd ~ wsl --unregister YunoHost wsl --import YunoHost .\WSL\YunoHost .\WSL\YunoHost.tar.gz --version 2 @@ -580,7 +580,7 @@ If you have one or more hard drives to store data, you can choose to mount it on | `/home/yunohost.backup/archives` | YunoHost backups to be placed ideally elsewhere than on the disks that manage the data | | `/home/yunohost.app` | Heavy data from YunoHost applications (nextcloud, matrix...) | | `/home/yunohost.multimedia` | Heavy data shared between several applications | -| `/var/mail` | User mail +| `/var/mail` | User mail | If you want flexibility and don't want to (re)size partitions, you can also choose to mount on `/mnt/hdd` and follow this [tutorial to mount all these folders with `mount --bind`](/external_storage). @@ -610,7 +610,7 @@ However, it is possible to fix by yourself the image before to run the initial c To achieve this, you need to connect on your raspberry pi as root user [via SSH](/ssh) with the temporary password `yunohost`: -``` +```bash ssh root@yunohost.local ``` @@ -618,7 +618,7 @@ ssh root@yunohost.local Then run the following commands to work around the metronome issue: -``` +```bash mv /usr/bin/metronome{,.bkp} mv /usr/bin/metronomectl{,.bkp} ln -s /usr/bin/true /usr/bin/metronome @@ -627,7 +627,7 @@ ln -s /usr/bin/true /usr/bin/metronomectl And this one to work around the upnpc issue: -``` +```bash sed -i 's/import miniupnpc/#import miniupnpc/g' /usr/lib/moulinette/yunohost/firewall.py ``` @@ -639,7 +639,7 @@ sed -i 's/import miniupnpc/#import miniupnpc/g' /usr/lib/moulinette/yunohost/fir Next you need to [find the local IP address of your server](/finding_the_local_ip) to connect as root user [via SSH](/ssh) with the temporary password `1234`. -``` +```bash ssh root@192.168.x.xxx ``` @@ -723,13 +723,13 @@ For example, `ynh.wsl`. The tricky part is advertising this domain to your host. Alter your `C:\Windows\System32\drivers\etc\hosts` file. You should have a line starting by `::1`, update it or add it if needed to get: -``` +```text ::1 ynh.wsl localhost ``` If you want to create subdomains, do not forget to add them in the `hosts` file too: -``` +```text ::1 ynh.wsl subdomain.ynh.wsl localhost ``` @@ -769,7 +769,7 @@ To run a diagnosis, go on Web Admin in the Diagnosis section. Click Run initial [/ui-tab] [ui-tab title="From the command line"] -``` +```bash yunohost diagnosis run yunohost diagnosis show --issues --human-readable ``` @@ -795,7 +795,7 @@ Go in Domains > Click on your domain > SSL Certificate [/ui-tab] [ui-tab title="From the command line"] -``` +```bash yunohost domain cert install ``` diff --git a/pages/02.administer/15.admin_guide/05.guidelines/guidelines.de.md b/pages/02.administer/15.admin_guide/05.guidelines/guidelines.de.md index bc59c982..ef05baeb 100644 --- a/pages/02.administer/15.admin_guide/05.guidelines/guidelines.de.md +++ b/pages/02.administer/15.admin_guide/05.guidelines/guidelines.de.md @@ -21,7 +21,7 @@ Ist Ihr Ziel, einen Produktionserver zu benutzen, so beachten Sie folgendes : - Vorsicht mit inoffiziellen Anwendungen, und verzichten auf solche, die noch "in Bearbeitung" sind, oder einen Level 0 haben ; - wenn etwas kaputt geht, überlegen Sie richtig, bevor Sie versuchen, es selbst zu reparieren, wenn Sie nicht wissen, was Sie tun. (z. B., den Admin-Benutzer nicht selbst versuchen neu anzulegen, falls er komischerweise verschwunden ist.) -## Keep it simple +## Keep it simple ! YunoHost ist für allgemeine und einfache Anwendungsfälle konzipiert. Wenn Sie von diesen Bedingungen abweichen, wird es schwieriger, und Sie benötigen technisches Wissen, um sie zu erfüllen. Zum Beispiel: diff --git a/pages/02.administer/15.admin_guide/05.guidelines/guidelines.fr.md b/pages/02.administer/15.admin_guide/05.guidelines/guidelines.fr.md index 13e76c31..bfea2ab4 100644 --- a/pages/02.administer/15.admin_guide/05.guidelines/guidelines.fr.md +++ b/pages/02.administer/15.admin_guide/05.guidelines/guidelines.fr.md @@ -21,7 +21,7 @@ Si votre but est d'avoir un serveur de production : - utilisez les applications non-officielles avec prudence, et interdisez-vous d'utiliser celles marquées 'in progress', 'not working' ou qui sont en niveau 0 ; - si quelque chose casse, réfléchissez à deux fois avant de tenter de le réparer vous-même si vous ne savez pas ce que vous faites. (Par exemple, n'essayez pas de recréer vous-même l'utilisateur admin juste parce qu'il a mystérieusement disparu...) -## Keep it simple +## Restez simple ! YunoHost est conçu pour fonctionner avec des cas d'utilisation généraux et simples. S'écarter de ces conditions rendra les choses plus difficiles et vous aurez besoin de connaissances techniques pour les faire fonctionner. Par exemple : diff --git a/pages/02.administer/15.admin_guide/05.guidelines/guidelines.it.md b/pages/02.administer/15.admin_guide/05.guidelines/guidelines.it.md index cb0eb77d..e1ba2ab1 100644 --- a/pages/02.administer/15.admin_guide/05.guidelines/guidelines.it.md +++ b/pages/02.administer/15.admin_guide/05.guidelines/guidelines.it.md @@ -21,7 +21,7 @@ Se il tuo obiettivo è avere un server in produzione: - usa le applicazioni non ufficiali con prudenza, e evita di usare quelle 'in progress', 'not working' o che hanno un livello 0; - se qualcosa dovesse rompersi, pensate due volte prima di cercare di riparare da soli se non sapete quello che state facendo. (Per esempio, non tentate di ricreare da soli l'utente admin solo perché sembra che sia misteriosamente scomparso...) -## Keep it simple +## Keep it simple ! YunoHost è progettato per funzionare in casi d'uso generici e semplici. Deviare da queste condizioni renderà le cose più difficili e avrai bisogno di conoscenze tecniche perché tutto funzioni. Per esempio: diff --git a/pages/02.administer/15.admin_guide/05.guidelines/guidelines.md b/pages/02.administer/15.admin_guide/05.guidelines/guidelines.md index 202f6779..9085bb66 100644 --- a/pages/02.administer/15.admin_guide/05.guidelines/guidelines.md +++ b/pages/02.administer/15.admin_guide/05.guidelines/guidelines.md @@ -21,7 +21,7 @@ If your goal is to run a production server: - use non-official apps with caution, and do not use apps that are still 'in progress', 'not working' or level 0; - if something gets broken, think twice about fixing it by yourself if you don't know what you are doing. (For instance, do not attempt to recreate yourself the admin user just because it mysteriously disappeared...) -## Keep it simple +## Keep it simple! YunoHost is designed to work with general and simple use cases in mind. Deviating from those conditions will make things harder and you will need technical knowledge to make it work. For instance: diff --git a/pages/02.administer/15.admin_guide/10.admin/admin.de.md b/pages/02.administer/15.admin_guide/10.admin/admin.de.md index e2bbe2d5..8167477e 100644 --- a/pages/02.administer/15.admin_guide/10.admin/admin.de.md +++ b/pages/02.administer/15.admin_guide/10.admin/admin.de.md @@ -11,6 +11,6 @@ YunoHost hat ein Administrator-Webinterface. Die andere Möglichkeit, Ihre YunoH ### Zugang -Sie können auf Ihr Administrator-Webinterface unter folgender Adresse zugreifen: (ersetzen Sie 'example.org' durch Ihren eigenen Domainnamen) +Sie können auf Ihr Administrator-Webinterface unter folgender Adresse zugreifen: (ersetzen Sie `example.org` durch Ihren eigenen Domainnamen) ![](image://webadmin.png) diff --git a/pages/02.administer/15.admin_guide/10.admin/admin.es.md b/pages/02.administer/15.admin_guide/10.admin/admin.es.md index f2668751..03594b19 100644 --- a/pages/02.administer/15.admin_guide/10.admin/admin.es.md +++ b/pages/02.administer/15.admin_guide/10.admin/admin.es.md @@ -11,6 +11,6 @@ YunoHost tiene una interfaz gráfica de administración. El otro método consist ### Acceso -La interfaz admin está accesible desde tu instancia YunoHost en esta dirección : (reemplaza ejemplo.org por tu nombre de dominio) +La interfaz admin está accesible desde tu instancia YunoHost en esta dirección : (reemplaza `ejemplo.org` por tu nombre de dominio) ![](image://webadmin.png) diff --git a/pages/02.administer/15.admin_guide/10.admin/admin.fr.md b/pages/02.administer/15.admin_guide/10.admin/admin.fr.md index 3d3f6d0e..6a7f462e 100644 --- a/pages/02.administer/15.admin_guide/10.admin/admin.fr.md +++ b/pages/02.administer/15.admin_guide/10.admin/admin.fr.md @@ -11,6 +11,6 @@ YunoHost est fourni avec une interface graphique d’administration (aussi appel ### Accès -L’interface d'administration web est accessible depuis votre instance YunoHost à l’adresse (remplacez exemple.org par la bonne valeur) +L’interface d'administration web est accessible depuis votre instance YunoHost à l’adresse (remplacez `exemple.org` par la bonne valeur) ![](image://webadmin_fr.png) diff --git a/pages/02.administer/15.admin_guide/10.admin/admin.it.md b/pages/02.administer/15.admin_guide/10.admin/admin.it.md index 93901cbb..173fa1e9 100644 --- a/pages/02.administer/15.admin_guide/10.admin/admin.it.md +++ b/pages/02.administer/15.admin_guide/10.admin/admin.it.md @@ -11,6 +11,6 @@ YunoHost ha un'interfaccia web di amministrazione. L'altro metodo è quello di u ### Accesso -L'interfaccia di amministrazione è accessibile all'indirizzo (sostituisci 'example.org' con il tuo dominio) +L'interfaccia di amministrazione è accessibile all'indirizzo (sostituisci `example.org` con il tuo dominio) ![](image://webadmin.png) diff --git a/pages/02.administer/15.admin_guide/10.admin/admin.md b/pages/02.administer/15.admin_guide/10.admin/admin.md index 5e917ba8..be5246d2 100644 --- a/pages/02.administer/15.admin_guide/10.admin/admin.md +++ b/pages/02.administer/15.admin_guide/10.admin/admin.md @@ -11,6 +11,6 @@ YunoHost has an administrator web interface. The other way to administrate your ### Access -You can access your administrator web interface at this address: (replace 'example.org' with your own domain name) +You can access your administrator web interface at this address: (replace `example.org` with your own domain name) ![](image://webadmin.png) diff --git a/pages/02.administer/15.admin_guide/15.command_line/command_line.de.md b/pages/02.administer/15.admin_guide/15.command_line/command_line.de.md index 760d9088..bd5d81f3 100644 --- a/pages/02.administer/15.admin_guide/15.command_line/command_line.de.md +++ b/pages/02.administer/15.admin_guide/15.command_line/command_line.de.md @@ -40,11 +40,11 @@ Es wird nach einem Passwort gefragt. Handelt es sich um einen VPS, sollte der VP ! Seit YunoHost 3.4 kann man sich nach dem Ausführen der Postinstallation nicht mehr als `root` anmelden. **Stattdessen sollte man sich mit dem `admin` Benutzer anmelden!** Für den Fall, dass der LDAP-Server defekt und der `admin` Benutzer nicht verwendbar ist, kann man sich eventuell trotzdem noch mit `root` über das lokale Netzwerk anmelden. -### Ändere das Passwort +### Ändere das Passwort! Nach dem allerersten Login sollte man das root Passwort ändern. Der Server könnte dazu automatisch auffordern. Falls nicht, ist der Befehl `passwd` zu benutzen. Es ist wichtig, ein einigermaßen starkes Passwort zu wählen. Beachte, dass das root Passwort durch das admin Passwort überschrieben wird, wenn man die Postinstallation durchführt. -### Auf ans Konfigurieren +### Auf ans Konfigurieren! Wir sind nun bereit, mit der [Postinstallation](/postinstall) zu beginnen. @@ -108,7 +108,7 @@ Eine ausführlichere Diskussion über Sicherheit & SSH findest du auf der [dedic !!! Ein vollständiges Tutorial über die Kommandozeile würde den Rahmen der YunoHost-Dokumentation sprengen: Lies dazu am besten ein spezielles Tutorial wie [dieses](https://ryanstutorials.net/linuxtutorial/) oder [dieses](http://linuxcommand.org/). Aber sei versichert, dass du kein CLI-Experte sein musst, um es zu benutzen! -Der Befehl "YunoHost" kann zur Verwaltung deines Servers verwendet werden und führt verschiedene Aktionen aus, die denen des Webadmin ähneln. Der Befehl muss entweder vom `root`-Benutzer oder vom `admin`-Benutzer durch Voranstellen von `sudo` gestartet werden. (ProTip™ : Du kannst `root` mit dem Befehl `sudo su` als `admin` werden). +Der Befehl `yunohost` kann zur Verwaltung deines Servers verwendet werden und führt verschiedene Aktionen aus, die denen des Webadmin ähneln. Der Befehl muss entweder vom `root`-Benutzer oder vom `admin`-Benutzer durch Voranstellen von `sudo` gestartet werden. (ProTip™ : Du kannst `root` mit dem Befehl `sudo su` als `admin` werden). YunoHost-Befehle haben normalerweise diese Art von Struktur: diff --git a/pages/02.administer/15.admin_guide/15.command_line/command_line.es.md b/pages/02.administer/15.admin_guide/15.command_line/command_line.es.md index ec5c0fec..abed9b90 100644 --- a/pages/02.administer/15.admin_guide/15.command_line/command_line.es.md +++ b/pages/02.administer/15.admin_guide/15.command_line/command_line.es.md @@ -41,7 +41,7 @@ Ahora te piden una contraseña. Si es un VPS, tu proveedor ya te hará comunicad ! Desde YunoHost 3.4, después de la post-instalación ya no es posible conectarse con el usuario `root`. En lugar de eso, hace falta **conectarse con el usuario `admin`**. Incluso si el servidor LDAP fuera quebrado (haciendo que el usuario `admin` ya no fuera utilizable) todavía deberías poder conectarte con el usuario `root` desde la red local. -### ¡ Cambiar la contraseña root +### ¡ Cambiar la contraseña root ! Después de haberte conectado por primera vez, tienes que cambiar la contraseña `root`. Tal vez el servidor te pida automáticamente que lo hagas. Si no es el caso, hay que utilizar el comando `passwd`. Es muy importante que elijas una contraseña bastante complicada. Nota que esta contraseña luego estará reemplazada por la contraseña admin elegida durante la post-instalación. diff --git a/pages/02.administer/15.admin_guide/30.apps/apps.fr.md b/pages/02.administer/15.admin_guide/30.apps/apps.fr.md index b4ecf56b..f81e4ecd 100644 --- a/pages/02.administer/15.admin_guide/30.apps/apps.fr.md +++ b/pages/02.administer/15.admin_guide/30.apps/apps.fr.md @@ -61,7 +61,7 @@ Si vous voulez apprendre ou contribuer à l'empaquetage des applications, veuill Dans le contexte de YunoHost, il est assez courant d'avoir un seul (ou quelques) domaines sur lesquels plusieurs applications sont installées dans des "sous-chemins", de sorte que l'on se retrouve avec quelque chose comme ceci : -```bash +```text yolo.com ├─── /blog : Wordpress (un blog) ├─── /cloud : Nextcloud (un service de cloud) diff --git a/pages/02.administer/15.admin_guide/30.apps/apps.it.md b/pages/02.administer/15.admin_guide/30.apps/apps.it.md index f04aa27d..2dae0e70 100644 --- a/pages/02.administer/15.admin_guide/30.apps/apps.it.md +++ b/pages/02.administer/15.admin_guide/30.apps/apps.it.md @@ -64,7 +64,7 @@ Questo può sembrare più facile per gli utenti finali ma è considerato più co Se le applicazioni dell'esempio precedente fossero state installate su un dominio separato questo potrebbe essere il risultato: -```bash +```text blog.yolo.com : Wordpress (a blog) cloud.yolo.com : Nextcloud (a cloud service) rss.yolo.com : TinyTiny RSS (a RSS reader) diff --git a/pages/02.administer/15.admin_guide/30.apps/apps.md b/pages/02.administer/15.admin_guide/30.apps/apps.md index 169a3eed..7630155c 100644 --- a/pages/02.administer/15.admin_guide/30.apps/apps.md +++ b/pages/02.administer/15.admin_guide/30.apps/apps.md @@ -46,7 +46,7 @@ Among specific questions, forms usually ask you to choose a domain and a path on In the context of YunoHost, it is quite common to have a single (or a few) domains on which several apps are installed in "subpaths", so that you end up with something like this: -```bash +```text yolo.com ├── /blog : Wordpress (a blog) ├── /cloud : Nextcloud (a cloud service) diff --git a/pages/02.administer/15.admin_guide/55.upgrade/10.stretch_buster_migration/stretch_buster_migration.md b/pages/02.administer/15.admin_guide/55.upgrade/10.stretch_buster_migration/stretch_buster_migration.md index 42366a5b..e7498578 100644 --- a/pages/02.administer/15.admin_guide/55.upgrade/10.stretch_buster_migration/stretch_buster_migration.md +++ b/pages/02.administer/15.admin_guide/55.upgrade/10.stretch_buster_migration/stretch_buster_migration.md @@ -25,7 +25,7 @@ After upgrading to 3.8.5.x, go to Tools > Migrations to access the migrations in ### From the command line -After upgrading to 3.8.5.x, run : +After upgrading to 3.8.5.x, run: ```bash sudo yunohost tools migrations migrate diff --git a/pages/02.administer/15.admin_guide/55.upgrade/15.buster_bullseye/buster_bullseye_migration.md b/pages/02.administer/15.admin_guide/55.upgrade/15.buster_bullseye/buster_bullseye_migration.md index c49187c2..d2fc0453 100644 --- a/pages/02.administer/15.admin_guide/55.upgrade/15.buster_bullseye/buster_bullseye_migration.md +++ b/pages/02.administer/15.admin_guide/55.upgrade/15.buster_bullseye/buster_bullseye_migration.md @@ -27,7 +27,7 @@ After upgrading to 4.4.x, go to Tools > Migrations to access the migrations inte ### From the command line -After upgrading to 4.4.x, run : +After upgrading to 4.4.x, run: ```bash sudo yunohost tools migrations run diff --git a/pages/02.administer/20.backups/05.evaluate/evaluate.md b/pages/02.administer/20.backups/05.evaluate/evaluate.md index 57d67d98..6a96dc5c 100644 --- a/pages/02.administer/20.backups/05.evaluate/evaluate.md +++ b/pages/02.administer/20.backups/05.evaluate/evaluate.md @@ -14,13 +14,13 @@ In the context of self-hosting, backups are an important element to compensate f ## What is a good backup ? -A good backup consists of at least **3 copies of the data**- (including the original data), on at least **2 separate storages**, in at least **2 separate locations** - (far enough apart) and ideally with 2 separate methods. If your backups are encrypted **these rules also apply to the decryption phrase/key**. +A good backup consists of at least **3 copies of the data** (including the original data), on at least **2 separate storages**, in at least **2 separate locations** (far enough apart) and ideally with 2 separate methods. If your backups are encrypted **these rules also apply to the decryption phrase/key**. -A good backup is also in many cases, a recent backup, so it takes either a lot of rigor or to **automate*- the process. +A good backup is also in many cases, a recent backup, so it takes either a lot of rigor or to **automate** the process. A good backup is checked regularly to ensure the effectiveness and integrity of the data. -Finally, a good backup is one that is **restorable within an acceptable timeframe*- for you. Remember to document your restoration method and to estimate the transfer time of a copy, especially if the Internet connections involved are not symmetrical. +Finally, a good backup is one that is **restorable within an acceptable timeframe** for you. Remember to document your restoration method and to estimate the transfer time of a copy, especially if the Internet connections involved are not symmetrical. !!! Example of **a robust and comfortable combination**: diff --git a/pages/02.administer/20.backups/30.custom_backup_methods/custom_backup_methods.it.md b/pages/02.administer/20.backups/30.custom_backup_methods/custom_backup_methods.it.md index 7ff8bbc7..ab1b9559 100644 --- a/pages/02.administer/20.backups/30.custom_backup_methods/custom_backup_methods.it.md +++ b/pages/02.administer/20.backups/30.custom_backup_methods/custom_backup_methods.it.md @@ -10,7 +10,6 @@ page-toc: depth: 3 --- - È possibile creare un proprio metodo di backup e includerlo nel sistema di raccolta file di backup di YunoHost. Questo può essere utilizzato ad esempio, nel caso utilizziate un particolare programma di backup o vogliate effettuare delle operazioni di montaggio o smontaggio sui vostri HD. Dovrete creare un hook che lancerà il backup utilizzando il metodo personalizzato con questo comando: diff --git a/pages/02.administer/20.backups/30.custom_backup_methods/custom_backup_methods.md b/pages/02.administer/20.backups/30.custom_backup_methods/custom_backup_methods.md index b79a067e..2c542042 100644 --- a/pages/02.administer/20.backups/30.custom_backup_methods/custom_backup_methods.md +++ b/pages/02.administer/20.backups/30.custom_backup_methods/custom_backup_methods.md @@ -10,7 +10,6 @@ page-toc: depth: 3 --- - It is possible to create your own backup method and link it to YunoHost's backup file collection system. This can be useful if you want to use your own backup software or conduct disk mount/dismount operations for example. This operation is done with a hook and will allow you to launch a backup this way: diff --git a/pages/02.administer/45.tutorials/05.domains/03.dns_subdomains/dns_subdomains.fr.md b/pages/02.administer/45.tutorials/05.domains/03.dns_subdomains/dns_subdomains.fr.md index 57806f43..997792b1 100644 --- a/pages/02.administer/45.tutorials/05.domains/03.dns_subdomains/dns_subdomains.fr.md +++ b/pages/02.administer/45.tutorials/05.domains/03.dns_subdomains/dns_subdomains.fr.md @@ -38,7 +38,7 @@ L’application est alors accessible via `blog.mondomaine.fr` (et non via `mondo ### Déplacer une application sur un sous-domaine ? Que se passe-t-il si on a déjà installé l’application ? On veut par exemple passer de `mondomaine.fr/wordpress` à `blog.mondomaine.fr`. -Pour l’instant il n’y a pas de façon simple (via l’interface graphique de l’administration de YunoHost) pour déplacer une application sur un sous-domaine. +Pour l’instant il n’y a pas de façon simple (via l’interface graphique de l’administration de YunoHost : Applications > nom_de_lapp > Modifier l’URL) pour déplacer une application sur un sous-domaine. Solution : réinstaller l’application diff --git a/pages/02.administer/45.tutorials/05.domains/03.dns_subdomains/dns_subdomains.md b/pages/02.administer/45.tutorials/05.domains/03.dns_subdomains/dns_subdomains.md index 549ebad7..3676d3fb 100644 --- a/pages/02.administer/45.tutorials/05.domains/03.dns_subdomains/dns_subdomains.md +++ b/pages/02.administer/45.tutorials/05.domains/03.dns_subdomains/dns_subdomains.md @@ -40,7 +40,7 @@ The application is then available at `blog.mydomain.com` (and not `mydomain.com/ What happens if the application is already installed? For example, one wants to move `mydomain.com/wordpress` to `blog.mydomain.com`. It depends on the application. -Some applications allow the change of domain. In that case, one can proceed to the change through the administration panel Applications > the_app_name > change URL. +Some applications allow the change of domain. In that case, one can proceed to the change through the administration panel: Applications > the_app_name > change URL. If the application doesn't allow URL change, then there is no easy way to do it. The best solution is to reinstall the application. ### Reinstalling an application diff --git a/pages/02.administer/45.tutorials/25.external_storage/external_storage.fr.md b/pages/02.administer/45.tutorials/25.external_storage/external_storage.fr.md index e04765b7..3f91f1b9 100644 --- a/pages/02.administer/45.tutorials/25.external_storage/external_storage.fr.md +++ b/pages/02.administer/45.tutorials/25.external_storage/external_storage.fr.md @@ -127,7 +127,7 @@ mount /dev/VOTRE_DISQUE1 /mnt/hdd (Ici, `/dev/VOTRE_DISQUE1` correspond à la première partition sur le disque) -## 5. Monter un dossier de /mnt/hdd sur un des dossiers dont on veut déplacer les données +## 5. Monter un dossier de `/mnt/hdd` sur un des dossiers dont on veut déplacer les données Ici on va considérer que vous souhaitez déplacer les grosses données des applications qui se trouvent dans `/home/yunohost.app` ainsi que les mails sur votre disque dur. @@ -248,6 +248,6 @@ rm -Rf /home/yunohost.app.bkp rm -Rf /var/mail.bkp ``` -## ![](image://tada.png?resize=32&classes=inline) Félicitations +## ![](image://tada.png?resize=32&classes=inline) Félicitations ! Si vous êtes arrivé jusqu'ici sans dommage, vous avez désormais un serveur qui tire parti d'un ou de plusieurs disques de stockage. diff --git a/pages/02.administer/45.tutorials/25.external_storage/external_storage.it.md b/pages/02.administer/45.tutorials/25.external_storage/external_storage.it.md index 2eca1f14..f418362d 100644 --- a/pages/02.administer/45.tutorials/25.external_storage/external_storage.it.md +++ b/pages/02.administer/45.tutorials/25.external_storage/external_storage.it.md @@ -127,7 +127,7 @@ mount /dev/miodisco /mnt/hdd (In questo caso, `/dev/miodisco` corrisponde alla prima partizione del disco) -## 5. Montare una cartella /mnt/hdd nella cartella che contiene i dati da spostare +## 5. Montare una cartella `/mnt/hdd` nella cartella che contiene i dati da spostare Ipotizzeremo, di seguito, lo spostamento delle mail e di una notevole quantità di dati delle applicazioni, che si trovano in `/home/yunohost.app`. @@ -248,6 +248,6 @@ rm -Rf /home/yunohost.app.bkp rm -Rf /var/mail.bkp ``` -### ![](image://tada.png?resize=32&classes=inline) Complimenti +### ![](image://tada.png?resize=32&classes=inline) Complimenti!!! Se siete giunti fino qui senza incidenti, avete configurato un server che sfrutta uno o più dischi per il salvataggio dei dati. diff --git a/pages/02.administer/45.tutorials/25.external_storage/external_storage.md b/pages/02.administer/45.tutorials/25.external_storage/external_storage.md index 6f7118b6..de63071f 100644 --- a/pages/02.administer/45.tutorials/25.external_storage/external_storage.md +++ b/pages/02.administer/45.tutorials/25.external_storage/external_storage.md @@ -42,16 +42,16 @@ Below is an explanation of some of the paths that can take up weight with some c | Paths | Contents | Tips | |--------|---|---| | `/home` | User folders accessible via SFTP | Moveable to a hard disk | -| `/home/yunohost.backup` | YunoHost's backups | Depending on your backup strategy, you may want to place this folder on a separate drive from your data or databases. -| `/home/yunohost.app` |Heavy data from YunoHost applications (nextcloud, matrix...)|Moveable to a hard disk +| `/home/yunohost.backup` | YunoHost's backups | Depending on your backup strategy, you may want to place this folder on a separate drive from your data or databases. | +| `/home/yunohost.app` |Heavy data from YunoHost applications (nextcloud, matrix...)|Moveable to a hard disk | | `/home/yunohost.multimedia` | Heavy data shared between several applications | Moveable to a hard disk | | `/var/lib/mysql` | Database used by applications | Ideally leave on SSD for performance reasons | | `/var/lib/postgresql` | Database used by applications | Ideally leave on SSD for performance reasons | | `/var/mail` | User e-mails | Movable to a hard disk | | `/var/www` | Program of installed web applications | Ideally leave on SSD for performance reasons | -| `/var/log` | Event logs (pages consulted, connection attempts, hardware errors...). | This directory should not take up too much space, if it grows quickly, it may be a looping error that should be resolved. -| `/opt` | Program and dependency of some YunoHost applications. | Ideally leave it on the SSD for performance reasons. For nodejs applications it is possible to do some cleanup of unused versions. -| `/boot` | Kernels and boot files | Do not move unless you know what you are doing. It can happen that too many kernels are kept, it is possible to do some cleanup. +| `/var/log` | Event logs (pages consulted, connection attempts, hardware errors...). | This directory should not take up too much space, if it grows quickly, it may be a looping error that should be resolved. | +| `/opt` | Program and dependency of some YunoHost applications. | Ideally leave it on the SSD for performance reasons. For nodejs applications it is possible to do some cleanup of unused versions. | +| `/boot` | Kernels and boot files | Do not move unless you know what you are doing. It can happen that too many kernels are kept, it is possible to do some cleanup. | ## 2. Connect and identify the disk @@ -246,6 +246,6 @@ rm -Rf /home/yunohost.app.bkp rm -Rf /var/mail.bkp ``` -## ![](image://tada.png?resize=32&classes=inline) Congratulations +## ![](image://tada.png?resize=32&classes=inline) Congratulations! If you have made it this far without damage, you now have a server that takes advantage of one or more storage disks. diff --git a/pages/02.administer/45.tutorials/40.tor/torhiddenservice.fr.md b/pages/02.administer/45.tutorials/40.tor/torhiddenservice.fr.md index f97d9c75..6877e91a 100644 --- a/pages/02.administer/45.tutorials/40.tor/torhiddenservice.fr.md +++ b/pages/02.administer/45.tutorials/40.tor/torhiddenservice.fr.md @@ -19,7 +19,7 @@ apt install tor Éditer le fichier `/etc/tor/torrc`, et ajouter ces lignes : -```bash +```text HiddenServiceDir /var/lib/tor/hidden_service/ HiddenServicePort 80 127.0.0.1:80 HiddenServicePort 443 127.0.0.1:443 diff --git a/pages/02.administer/45.tutorials/40.tor/torhiddenservice.it.md b/pages/02.administer/45.tutorials/40.tor/torhiddenservice.it.md index 658b8264..431d5737 100644 --- a/pages/02.administer/45.tutorials/40.tor/torhiddenservice.it.md +++ b/pages/02.administer/45.tutorials/40.tor/torhiddenservice.it.md @@ -19,7 +19,7 @@ apt install tor Modifica `/etc/tor/torrc` aggiungendo queste righe: -```bash +```text HiddenServiceDir /var/lib/tor/hidden_service/ HiddenServicePort 80 127.0.0.1:80 HiddenServicePort 443 127.0.0.1:443 diff --git a/pages/02.administer/45.tutorials/40.tor/torhiddenservice.md b/pages/02.administer/45.tutorials/40.tor/torhiddenservice.md index 1188289a..5b636df6 100644 --- a/pages/02.administer/45.tutorials/40.tor/torhiddenservice.md +++ b/pages/02.administer/45.tutorials/40.tor/torhiddenservice.md @@ -19,7 +19,7 @@ apt install tor Edit `/etc/tor/torrc`, and add these lines: -```bash +```text HiddenServiceDir /var/lib/tor/hidden_service/ HiddenServicePort 80 127.0.0.1:80 HiddenServicePort 443 127.0.0.1:443 diff --git a/pages/02.administer/45.tutorials/45.certificate_custom/certificate_custom.fr.md b/pages/02.administer/45.tutorials/45.certificate_custom/certificate_custom.fr.md index 9860165f..ad516539 100644 --- a/pages/02.administer/45.tutorials/45.certificate_custom/certificate_custom.fr.md +++ b/pages/02.administer/45.tutorials/45.certificate_custom/certificate_custom.fr.md @@ -17,7 +17,7 @@ Quelques changements ont eu lieu qui impactent les procédures indiquées ci-des ### Ajout d’un certificat signé par une autorité (autre que Let's Encrypt) Après création du certificat auprès de votre autorité d’enregistrement, vous devez être en possession d’une clé privée, le fichier *key* et d’un certificat public, le fichier *crt*. -Attention, le fichier *key* est très sensible, il est strictement personnel et doit être très bien sécurisé. +! Attention, le fichier *key* est très sensible, il est strictement personnel et doit être très bien sécurisé. Ces deux fichiers doivent être copiés sur le serveur, s’ils ne s’y trouvent pas déjà. @@ -57,26 +57,26 @@ sudo mv *.pem *.cnf yunohost_self_signed/ En fonction de l’autorité d’enregistrement, des certificats intermédiaires et racines doivent être obtenus. -**StartSSL** +#### StartSSL ```bash sudo wget http://www.startssl.com/certs/ca.pem -O ae_certs/ca.pem sudo wget http://www.startssl.com/certs/sub.class1.server.ca.pem -O ae_certs/intermediate_ca.pem ``` -**Gandi** +#### Gandi ```bash sudo wget https://www.gandi.net/static/CAs/GandiStandardSSLCA2.pem -O ae_certs/intermediate_ca.pem ``` -**RapidSSL** +#### RapidSSL ```bash sudo wget https://knowledge.rapidssl.com/library/VERISIGN/INTERNATIONAL_AFFILIATES/RapidSSL/AR1548/RapidSSLCABundle.txt -O ae_certs/intermediate_ca.pem ``` -**Cacert** +#### Cacert ```bash sudo wget http://www.cacert.org/certs/root.crt -O ae_certs/ca.pem @@ -142,4 +142,4 @@ Rechargez la configuration de NGINX pour prendre en compte le nouveau certificat sudo service nginx reload ``` -Votre certificat est prêt à servir. Vous pouvez toutefois vous assurer de sa mise en place en testant le certificat à l’aide du service de geocerts. diff --git a/pages/02.administer/45.tutorials/45.certificate_custom/certificate_custom.md b/pages/02.administer/45.tutorials/45.certificate_custom/certificate_custom.md index 9e6c7248..a3375e12 100644 --- a/pages/02.administer/45.tutorials/45.certificate_custom/certificate_custom.md +++ b/pages/02.administer/45.tutorials/45.certificate_custom/certificate_custom.md @@ -17,7 +17,7 @@ Some changes have taken place which impact the procedures indicated below: ### Adding a signed certificate by an authority (other than Let's Encrypt) After the certificate creation with your registration authority, you must have a private key, the key file, and a public certificate, the crt file. -Note that the key file is very sensitive, it is strictly personal and must be very well secured. +! Note that the key file is very sensitive, it is strictly personal and must be very well secured. These two files should be copied to the server, if they are not already there. @@ -56,26 +56,26 @@ sudo mv *.pem *.cnf yunohost_self_signed/ Depending on the registration authority, intermediate and root certificates must be obtained. -**StartSSL** +#### StartSSL ```bash sudo wget http://www.startssl.com/certs/ca.pem -O ae_certs/ca.pem sudo wget http://www.startssl.com/certs/sub.class1.server.ca.pem -O ae_certs/intermediate_ca.pem ``` -**Gandi** +#### Gandi ```bash sudo wget https://www.gandi.net/static/CAs/GandiStandardSSLCA2.pem -O ae_certs/intermediate_ca.pem ``` -**RapidSSL** +#### RapidSSL ```bash sudo wget https://knowledge.rapidssl.com/library/VERISIGN/INTERNATIONAL_AFFILIATES/RapidSSL/AR1548/RapidSSLCABundle.txt -O ae_certs/intermediate_ca.pem ``` -**Cacert** +#### Cacert ```bash sudo wget http://www.cacert.org/certs/root.crt -O ae_certs/ca.pem @@ -141,4 +141,4 @@ Reload NGINX configuration to take into account the new certificate. sudo service nginx reload ``` -Your certificate is ready. However, you can ensure that it is in place by testing the certificate using the geocerts. diff --git a/pages/02.administer/50.troubleshooting/15.noaccess/noaccess.fr.md b/pages/02.administer/50.troubleshooting/15.noaccess/noaccess.fr.md index 1bd0b3a2..53405fd5 100644 --- a/pages/02.administer/50.troubleshooting/15.noaccess/noaccess.fr.md +++ b/pages/02.administer/50.troubleshooting/15.noaccess/noaccess.fr.md @@ -20,8 +20,8 @@ Vérifier que vous arrivez à accéder au serveur en utilisant son IP globale (q - Assurez-vous d'avoir [configuré les redirections de ports](/isp_box_config) - Certaines box de FAI ne supportent pas le hairpinning et vous ne pouvez pas accéder à votre serveur depuis l'intérieur du réseau local (sauf à passer par l'IP locale). Pour contourner le problème, vous pouvez utiliser un des moyens suivants: - utiliser une connexion cellulaire (4/5G) - - modifier le fichier /etc/hosts sur vos équipements - - déclarer l'ip locale de YunoHost comme resolveur DNS dans votre routeur (partie DHCP) et ouvrir le port 53 UDP sur votre YunoHost en faisant attention de ne pas activer l'upnp sur le port 53. Surtout, n'ouvrez pas le port 53 de votre routeur. + - modifier le fichier `/etc/hosts` sur vos équipements + - déclarer l'ip locale de YunoHost comme resolveur DNS dans votre routeur (partie DHCP) et ouvrir le port `53` UDP sur votre YunoHost en faisant attention de ne pas activer l'upnp sur le port `53`. Surtout, n'ouvrez pas le port `53` de votre routeur. ### Il faut configurer vos enregistrement DNS @@ -85,7 +85,7 @@ Dans certains, cas une mise à jour de votre box a activé l'IPv6, entraînant d ## La webadmin fonctionne, mais certaines applications web me renvoient une erreur 502 -Il est fort probablement que le service correspondant à ces applications soit en panne (typiquement pour les applications PHP, il s'agit de php7.0-fpm ou php7.3-fpm). Vous pouvez alors tenter de relancer le service, et si cela ne fonctionne pas, regarder les logs du service correspondant et/ou [demander de l'aide](/help). +Il est fort probablement que le service correspondant à ces applications soit en panne (typiquement pour les applications PHP, il s'agit de `php7.0-fpm` ou `php7.3-fpm`). Vous pouvez alors tenter de relancer le service, et si cela ne fonctionne pas, regarder les logs du service correspondant et/ou [demander de l'aide](/help). ## Vous avez perdu votre mot de passe administrateur ? (ou bien le mot de passe est refusé) diff --git a/pages/02.administer/50.troubleshooting/15.noaccess/noaccess.it.md b/pages/02.administer/50.troubleshooting/15.noaccess/noaccess.it.md index 2c7ddda4..309c30b0 100644 --- a/pages/02.administer/50.troubleshooting/15.noaccess/noaccess.it.md +++ b/pages/02.administer/50.troubleshooting/15.noaccess/noaccess.it.md @@ -69,7 +69,7 @@ Maybe the NGINX web server is out of order. You can check that [trough SSH](/ssh The NGINX or SSH servers may have been killed due to a lack of storage space, RAM, or swap. - Try restarting the service with `systemctl restart nginx`. -- You can check used storage with `df -h`. If one of your partitions is full, you need to identify what fills it and make rooù. You can use `ncdu` command (install it with `apt install ncdu` to browse from the root directory: `ncdu /` +- You can check used storage with `df -h`. If one of your partitions is full, you need to identify what fills it and make rooù. You can use `ncdu` command (install it with `apt install ncdu`) to browse from the root directory: `ncdu /` - You can check RAM and swap usage with `free -h`. Depending on the result, it may be necessary to optimize your server to use less RAM (removal of heavy or unused apps...), add more RAM or add a swap file. ### Your server is reachable by IPv6, but not IPv4, or inversely diff --git a/pages/02.administer/50.troubleshooting/15.noaccess/noaccess.md b/pages/02.administer/50.troubleshooting/15.noaccess/noaccess.md index 0e325371..e0034f7f 100644 --- a/pages/02.administer/50.troubleshooting/15.noaccess/noaccess.md +++ b/pages/02.administer/50.troubleshooting/15.noaccess/noaccess.md @@ -67,7 +67,7 @@ Maybe the NGINX web server is out of order. You can check that [trough SSH](/ssh The NGINX or SSH servers may have been killed due to a lack of storage space, RAM, or swap. - Try restarting the service with `systemctl restart nginx`. -- You can check used storage with `df -h`. If one of your partitions is full, you need to identify what fills it and make room. You can use `ncdu` command (install it with `apt install ncdu` to browse from the root directory: `ncdu /` +- You can check used storage with `df -h`. If one of your partitions is full, you need to identify what fills it and make room. You can use `ncdu` command (install it with `apt install ncdu`) to browse from the root directory: `ncdu /` - You can check RAM and swap usage with `free -h`. Depending on the result, it may be necessary to optimize your server to use less RAM (removal of heavy or unused apps...), add more RAM or add a swap file. ### Your server is reachable by IPv6, but not IPv4, or inversely diff --git a/pages/02.administer/50.troubleshooting/20.ipv6/ipv6.fr.md b/pages/02.administer/50.troubleshooting/20.ipv6/ipv6.fr.md index b74c60d6..3608073c 100644 --- a/pages/02.administer/50.troubleshooting/20.ipv6/ipv6.fr.md +++ b/pages/02.administer/50.troubleshooting/20.ipv6/ipv6.fr.md @@ -35,7 +35,7 @@ Sur votre VPS, vous allez créer une sauvegarde de votre fichier de configuratio ! Découvrir et vérifier avec la commande `ip a` l'interface utilisée sur votre VPS ( généralement du type ENS3 chez OVH) ! Dans cet exemple, nous considérons que votre interface réseau est `eth0`. Vous devez adapter l'exemple pour correspondre à votre situation. -```plaintext +```text iface eth0 inet6 static address netmask diff --git a/pages/02.administer/50.troubleshooting/20.ipv6/ipv6.it.md b/pages/02.administer/50.troubleshooting/20.ipv6/ipv6.it.md index a323f94d..b08ca6c3 100644 --- a/pages/02.administer/50.troubleshooting/20.ipv6/ipv6.it.md +++ b/pages/02.administer/50.troubleshooting/20.ipv6/ipv6.it.md @@ -31,7 +31,7 @@ Poi puoi modificare il file di configurazione (`/etc/network/interfaces`) come i ! In questo esempio si assume che il nome della tua interfaccia di rete sia `eth0`. Nel caso invece che sia differente (controlla con il comando `ip a`) devi adattare di conseguenza l'esempio qui sotto. -```plaintext +```text iface eth0 inet6 static address netmask diff --git a/pages/02.administer/50.troubleshooting/20.ipv6/ipv6.md b/pages/02.administer/50.troubleshooting/20.ipv6/ipv6.md index c0e3c655..b20b51c7 100644 --- a/pages/02.administer/50.troubleshooting/20.ipv6/ipv6.md +++ b/pages/02.administer/50.troubleshooting/20.ipv6/ipv6.md @@ -31,7 +31,7 @@ Then, you can edit the configuration file (`/etc/network/interfaces`) with the f ! In this example, it is assumed that your network interface is `eth0`. If it's different (check with `ip a`) you need to adapt the example below. -```plaintext +```text iface eth0 inet6 static address netmask diff --git a/pages/02.administer/50.troubleshooting/25.unblacklisting/blacklist_forms.md b/pages/02.administer/50.troubleshooting/25.unblacklisting/blacklist_forms.md index 94f80766..25152679 100644 --- a/pages/02.administer/50.troubleshooting/25.unblacklisting/blacklist_forms.md +++ b/pages/02.administer/50.troubleshooting/25.unblacklisting/blacklist_forms.md @@ -67,6 +67,6 @@ You can find a tool to test your IP, advices, explanation of error code and a wa If you use your own domains and think that some mails are sent by unauthorized servers (so without SPF/DKIM), you get report about this mail with. -```dns +```text _dmarc.DOMAIN 3600 IN TXT "v=DMARC1; p=none; fo=1; rua=mailto:example@domain.tld!10m" ``` diff --git a/pages/02.administer/55.providers/10.isp/isp.md b/pages/02.administer/55.providers/10.isp/isp.md index 5bd24c24..f8a97ce2 100644 --- a/pages/02.administer/55.providers/10.isp/isp.md +++ b/pages/02.administer/55.providers/10.isp/isp.md @@ -137,6 +137,7 @@ Tous les fournisseurs d’accès à Internet [membres de la Fédération French | **[IP fixe](/dns_dynamicip)** | ✔ | ✔ | ✔/✘ | ✘ (en option depuis la Livebox 3 et sur les abonnements orange pro) | ✔ | ✔ | | **[IPv6](https://fr.wikipedia.org/wiki/IPv6)** | ✔ | ✔ | ✔ | ✔ | … | … | | **[Non listé sur le DUL](https://en.wikipedia.org/wiki/Dialup_Users_List)** | … | ✘ | … | … | … | … | + Pour une liste plus complète et précise, référez-vous à la très bonne documentation de [wiki.auto-hebergement.fr](http://wiki.auto-hebergement.fr/fournisseurs/fai#d%C3%A9tail_des_fai). **Astuce** : [FDN](http://www.fdn.fr) fournit des [VPN](http://www.fdn.fr/-VPN-.html) permettant de rapatrier une (ou plusieurs sur demande) IPv4 fixe et un /48 en IPv6 et ainsi « nettoyer » votre connexion si vous êtes chez l’un des FAI *limitants* du tableau ci-dessus. diff --git a/pages/02.administer/55.providers/10.isp/orange/isp_orange.fr.md b/pages/02.administer/55.providers/10.isp/orange/isp_orange.fr.md index d6275a2f..de1a3654 100644 --- a/pages/02.administer/55.providers/10.isp/orange/isp_orange.fr.md +++ b/pages/02.administer/55.providers/10.isp/orange/isp_orange.fr.md @@ -28,7 +28,7 @@ sudo nano /etc/postfix/main.cf puis, rajouter à la ligne le relai SMTP d’Orange : -```bash +```text relayhost = smtp.orange.fr ``` diff --git a/pages/02.administer/55.providers/15.vpn/01.vpn/vpn_advantage.es.md b/pages/02.administer/55.providers/15.vpn/01.vpn/vpn_advantage.es.md index 997a4693..adda66ee 100644 --- a/pages/02.administer/55.providers/15.vpn/01.vpn/vpn_advantage.es.md +++ b/pages/02.administer/55.providers/15.vpn/01.vpn/vpn_advantage.es.md @@ -31,10 +31,10 @@ El correo es uno de los protocolos más complejos de autoalojar, normalmente es Para evitarlo, necesitas, entre otras cosas: - -configurar el DNS inverso de la conexión a Internet del servidor (o VPN) - -una IPv4 fija - -que esta IPv4 sea eliminada de todas las listas negras (en particular, la IP no debe estar en el DUL) - -poder abrir el puerto 25 (así como otros puertos SMTP) +- configurar el DNS inverso de la conexión a Internet del servidor (o VPN) +- una IPv4 fija +- que esta IPv4 sea eliminada de todas las listas negras (en particular, la IP no debe estar en el DUL) +- poder abrir el puerto 25 (así como otros puertos SMTP) Desgraciadamente, ninguno de los ISP franceses más habituales respeta todos estos puntos. @@ -56,5 +56,5 @@ Cuando se establece una VPN en el servidor, si no se establece una configuració Para superar este punto, hay dos soluciones: - -transformando su servidor en un router y conectando su equipo doméstico a él, este equipo se beneficiará también de la confidencialidad de la VPN. - -utilizar el servidor de YunoHost como resolvedor de DNS cuando estés en casa, para redirigir los nombres de dominio del servidor a la ip local en lugar de la ip pública. Esta operación puede realizarse en cada dispositivo o en el router (si éste lo permite). +- transformando su servidor en un router y conectando su equipo doméstico a él, este equipo se beneficiará también de la confidencialidad de la VPN. +- utilizar el servidor de YunoHost como resolvedor de DNS cuando estés en casa, para redirigir los nombres de dominio del servidor a la ip local en lugar de la ip pública. Esta operación puede realizarse en cada dispositivo o en el router (si éste lo permite). diff --git a/pages/02.administer/60.extend/30.api/admin_api.md b/pages/02.administer/60.extend/30.api/admin_api.md index 3956d9d0..fd49c76e 100644 --- a/pages/02.administer/60.extend/30.api/admin_api.md +++ b/pages/02.administer/60.extend/30.api/admin_api.md @@ -30,7 +30,7 @@ curl -k -i -H "Accept: application/json" \ ## Test with our swagger doc - 1. Login on the [Webadmin of demo.yunohost.org](https://demo.yunohost.org/yunohost/admin/) + 1. Login on the [Webadmin of `demo.yunohost.org`](https://demo.yunohost.org/yunohost/admin/) 2. Use the `Try it out` button on the API endpoint you want to test
@@ -39,10 +39,10 @@ curl -k -i -H "Accept: application/json" \ display: none; } - - - - + + + +