mirror of
https://github.com/YunoHost/doc.git
synced 2024-09-03 20:06:26 +02:00
Replace some apt-get with simply apt and remove a few unecessary sudo
This commit is contained in:
parent
dd7aa00a46
commit
4c982de95f
11 changed files with 34 additions and 34 deletions
|
@ -6,7 +6,7 @@ Once you have access to a command line on your server (either directly or throug
|
||||||
bash <(wget -q -O- https://install.yunohost.org/)
|
bash <(wget -q -O- https://install.yunohost.org/)
|
||||||
```
|
```
|
||||||
|
|
||||||
<small>*(If `wget` is not installed on your system, you might need to install it with `apt-get install wget`)*</small>
|
<small>*(If `wget` is not installed on your system, you might need to install it with `apt install wget`)*</small>
|
||||||
|
|
||||||
Once the installation is finished, you may want to [**proceed to post-installation**](/postinstall)
|
Once the installation is finished, you may want to [**proceed to post-installation**](/postinstall)
|
||||||
|
|
||||||
|
|
|
@ -88,7 +88,7 @@ After connecting, you will be asked to changed the root password. First, enter *
|
||||||
|
|
||||||
Update your server with the following commands. It can take around 15 minutes.
|
Update your server with the following commands. It can take around 15 minutes.
|
||||||
```bash
|
```bash
|
||||||
apt-get update && apt-get dist-upgrade
|
apt update && apt dist-upgrade
|
||||||
```
|
```
|
||||||
|
|
||||||
## Proceed to post-installation
|
## Proceed to post-installation
|
||||||
|
|
|
@ -86,7 +86,7 @@ ssh root@192.168.x.y
|
||||||
|
|
||||||
Mettre à jour le système (environ 15 minutes) :
|
Mettre à jour le système (environ 15 minutes) :
|
||||||
```bash
|
```bash
|
||||||
apt-get update && apt-get dist-upgrade
|
apt update && apt dist-upgrade
|
||||||
```
|
```
|
||||||
|
|
||||||
## Procéder à la postinstallation
|
## Procéder à la postinstallation
|
||||||
|
|
|
@ -41,7 +41,7 @@ Pour pouvoir envoyer des mails, passer le blocage en « inactif ».
|
||||||
|
|
||||||
Il faut installer le paquet `cifs-utils`
|
Il faut installer le paquet `cifs-utils`
|
||||||
```bash
|
```bash
|
||||||
$ sudo apt-get install cifs-utils
|
$ sudo apt install cifs-utils
|
||||||
```
|
```
|
||||||
|
|
||||||
Il faut créer un point de montage (ici `/home/monlogin/freebox`)
|
Il faut créer un point de montage (ici `/home/monlogin/freebox`)
|
||||||
|
|
|
@ -69,12 +69,12 @@ Si vous avez une erreur "(SASL authentication failed; cannot authenticate to ser
|
||||||
Vérifier la présence de libsasl2-modules et de sasl2-bin :
|
Vérifier la présence de libsasl2-modules et de sasl2-bin :
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
sudo apt-cache search libsasl2-modules
|
apt search libsasl2-modules
|
||||||
sudo apt-cache search sasl2-bin
|
apt search sasl2-bin
|
||||||
```
|
```
|
||||||
|
|
||||||
Si ils ne sont pas présents, installez-les :
|
Si ils ne sont pas présents, installez-les :
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
sudo apt-get install libsasl2-modules sasl2-bin
|
apt install libsasl2-modules sasl2-bin
|
||||||
```
|
```
|
||||||
|
|
|
@ -4,7 +4,7 @@ See https://www.torproject.org/docs/tor-hidden-service.html.en
|
||||||
|
|
||||||
### Installing Tor
|
### Installing Tor
|
||||||
```bash
|
```bash
|
||||||
sudo apt-get install tor
|
apt install tor
|
||||||
```
|
```
|
||||||
|
|
||||||
### Configuring our hidden service
|
### Configuring our hidden service
|
||||||
|
@ -43,4 +43,4 @@ If you want to avoid being redirected to the SSO portal at login, you can deacti
|
||||||
### Restart nginx
|
### Restart nginx
|
||||||
```bash
|
```bash
|
||||||
service nginx restart
|
service nginx restart
|
||||||
```
|
```
|
||||||
|
|
|
@ -4,7 +4,7 @@ Voir https://www.torproject.org/docs/tor-hidden-service.html.en (anglais)
|
||||||
|
|
||||||
### Installer Tor
|
### Installer Tor
|
||||||
```bash
|
```bash
|
||||||
sudo apt-get install tor
|
apt install tor
|
||||||
```
|
```
|
||||||
|
|
||||||
### Configurer notre service caché
|
### Configurer notre service caché
|
||||||
|
|
|
@ -27,13 +27,13 @@ Problems often occur after an upgrade. After a YunoHost upgrade you may want to
|
||||||
|
|
||||||
You are probably familiar with:
|
You are probably familiar with:
|
||||||
```bash
|
```bash
|
||||||
sudo apt-get update && sudo apt-get dist-upgrade
|
$ apt update && apt dist-upgrade
|
||||||
```
|
```
|
||||||
Most of the time it's enough. But in some cases it's possible that some process are still using old versions of upgraded files (such as libraries), that can cause bug. In rare cases that can lead to security concern (ex: upgrade OpenSSL because of a security bug, Nginx will continue to use the version it has in memory). The utility Checkrestart will help you to find and restart them.
|
Most of the time it's enough. But in some cases it's possible that some process are still using old versions of upgraded files (such as libraries), that can cause bug. In rare cases that can lead to security concern (ex: upgrade OpenSSL because of a security bug, Nginx will continue to use the version it has in memory). The utility Checkrestart will help you to find and restart them.
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
sudo apt-get install debian-goodies
|
$ apt install debian-goodies
|
||||||
sudo checkrestart
|
$ checkrestart
|
||||||
Found 0 processes using old versions of upgraded files
|
Found 0 processes using old versions of upgraded files
|
||||||
```
|
```
|
||||||
If some process are running with old librairies versions checkrestart will tell you and propose you a way to restart them. In some cases checkrestart can't find a way to restart them.
|
If some process are running with old librairies versions checkrestart will tell you and propose you a way to restart them. In some cases checkrestart can't find a way to restart them.
|
||||||
|
@ -48,10 +48,10 @@ You can also use [this script](https://github.com/octopuce/octopuce-goodies/blob
|
||||||
|
|
||||||
/!\ Always check if there is a upgrade script and read it if you can /!\
|
/!\ Always check if there is a upgrade script and read it if you can /!\
|
||||||
```bash
|
```bash
|
||||||
sudo yunohost app upgrade
|
$ yunohost app upgrade
|
||||||
Warning: You must provide an URL to upgrade your custom app app_name
|
Warning: You must provide an URL to upgrade your custom app app_name
|
||||||
Error: No app to upgrade
|
Error: No app to upgrade
|
||||||
sudo yunohost app upgrade -u https://github.com/user/someapp_ynh app_name
|
$ yunohost app upgrade -u https://github.com/user/someapp_ynh app_name
|
||||||
```
|
```
|
||||||
|
|
||||||
## Services
|
## Services
|
||||||
|
@ -61,7 +61,7 @@ YunoHost uses a bunch of software to accomplish its purpose. Most of theses soft
|
||||||
When something doesn't work on your YunoHost, one of the first things to do is to check that all services used by YunoHost are running.
|
When something doesn't work on your YunoHost, one of the first things to do is to check that all services used by YunoHost are running.
|
||||||
YunoHost include a helper to see the status of all services used by YunoHost:
|
YunoHost include a helper to see the status of all services used by YunoHost:
|
||||||
```bash
|
```bash
|
||||||
sudo yunohost service status
|
$ yunohost service status
|
||||||
```
|
```
|
||||||
|
|
||||||
Sample result:
|
Sample result:
|
||||||
|
@ -91,21 +91,20 @@ Others services installed by applications can also be present. For instance, `se
|
||||||
##### Start or stop a service which is registered with YunoHost:
|
##### Start or stop a service which is registered with YunoHost:
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
sudo yunohost service start <servicename>
|
$ yunohost service start <servicename>
|
||||||
sudo yunohost service stop <servicename>
|
$ yunohost service stop <servicename>
|
||||||
```
|
```
|
||||||
You can also use the generic Debian command:
|
You can also use the generic Debian command:
|
||||||
```bash
|
```bash
|
||||||
sudo systemctl start/stop/restart/reload <servicename>
|
$ systemctl start/stop/restart/reload <servicename>
|
||||||
```
|
```
|
||||||
After a launch attempt, always check that the service is running.
|
After a launch attempt, always check that the service is running.
|
||||||
|
|
||||||
### Logs
|
### Logs
|
||||||
If a service won't start you have to check the logs to see what's wrong. There is no generic way for services to store their logs, but there are mainly stocked in:
|
If a service won't start you have to check the logs to see what's wrong. There is no generic way for services to store their logs, but there are mainly stocked in: `/var/log/`
|
||||||
```bash
|
|
||||||
/var/log/
|
|
||||||
```
|
|
||||||
Here are the some useful logs files for YunoHost:
|
Here are the some useful logs files for YunoHost:
|
||||||
|
|
||||||
##### auth.log
|
##### auth.log
|
||||||
Contains connections or attempt of connection to your server. It includes every web, ssh, cron job connection. It also stockes all the failed (hopefully) attempts to connect by a potential intruders connections.
|
Contains connections or attempt of connection to your server. It includes every web, ssh, cron job connection. It also stockes all the failed (hopefully) attempts to connect by a potential intruders connections.
|
||||||
|
|
||||||
|
@ -227,7 +226,7 @@ You can view (don't edit it, it is oftently overwritten) your current SSOwat con
|
||||||
```
|
```
|
||||||
Which is generated with the command:
|
Which is generated with the command:
|
||||||
```bash
|
```bash
|
||||||
sudo yunohost app ssowatconf
|
yunohost app ssowatconf
|
||||||
```
|
```
|
||||||
Protip: if you want to add a personalized rule for SSOwat, do it in this file:
|
Protip: if you want to add a personalized rule for SSOwat, do it in this file:
|
||||||
```bash
|
```bash
|
||||||
|
@ -264,7 +263,7 @@ In each app packages you will find:
|
||||||
* **config/**: config directory
|
* **config/**: config directory
|
||||||
* **settings.yml**: config of the app, also accessible with:
|
* **settings.yml**: config of the app, also accessible with:
|
||||||
```bash
|
```bash
|
||||||
sudo yunohost app setting appname settingname
|
yunohost app setting appname settingname
|
||||||
```
|
```
|
||||||
|
|
||||||
### Logs
|
### Logs
|
||||||
|
|
|
@ -28,15 +28,15 @@ Les problèmes ont souvent lieu après une mise à jour. Après une mise à jour
|
||||||
**Vérifier si un processus utilise une ancienne librairie**
|
**Vérifier si un processus utilise une ancienne librairie**
|
||||||
vous avez sûrement l’habitude d’utiliser :
|
vous avez sûrement l’habitude d’utiliser :
|
||||||
```bash
|
```bash
|
||||||
sudo apt-get update && sudo apt-get dist-upgrade
|
$ apt update && apt dist-upgrade
|
||||||
```
|
```
|
||||||
La plupart du temps, cela suffit. Mais dans certaines situations, il est possible que certains processus utilisent toujours d’anciennes bibliothèques non mises à jour.
|
La plupart du temps, cela suffit. Mais dans certaines situations, il est possible que certains processus utilisent toujours d’anciennes bibliothèques non mises à jour.
|
||||||
Cela peut entraîner des bugs et, dans certains rares cas, des problèmes de sécurité (ex : lors d’une mise à jour de OpenSSL à cause d’une faille de sécurité, Nginx va continuer à utiliser la version dont il dispose en mémoire). L’utilitaire Checkrestart va vous aider à identifier ces processus et les redémarrer.
|
Cela peut entraîner des bugs et, dans certains rares cas, des problèmes de sécurité (ex : lors d’une mise à jour de OpenSSL à cause d’une faille de sécurité, Nginx va continuer à utiliser la version dont il dispose en mémoire). L’utilitaire Checkrestart va vous aider à identifier ces processus et les redémarrer.
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
sudo apt-get install debian-goodies
|
$ apt install debian-goodies
|
||||||
sudo checkrestart
|
checkrestart
|
||||||
Found 0 processes using old versions of upgraded files
|
# Found 0 processes using old versions of upgraded files
|
||||||
```
|
```
|
||||||
Si des processus fonctionnent avec des vieilles versions de bibliothèques, checkrestart va vous le dire et vous proposer une manière de les redémarrer. Il est possible que checkrestart ne trouve pas de manière de les redémarrer. Attention, il faut opérer l’opération manuellement.
|
Si des processus fonctionnent avec des vieilles versions de bibliothèques, checkrestart va vous le dire et vous proposer une manière de les redémarrer. Il est possible que checkrestart ne trouve pas de manière de les redémarrer. Attention, il faut opérer l’opération manuellement.
|
||||||
|
|
||||||
|
@ -52,10 +52,11 @@ Vous pouvez aussi utiliser [ce script](https://github.com/octopuce/octopuce-good
|
||||||
|
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
sudo yunohost app upgrade
|
$ yunohost app upgrade
|
||||||
Warning: You must provide an URL to upgrade your custom app app_name
|
Warning: You must provide an URL to upgrade your custom app app_name
|
||||||
Error: No app to upgrade
|
Error: No app to upgrade
|
||||||
sudo yunohost app upgrade -u https://github.com/user/someapp_ynh app_name
|
|
||||||
|
$ yunohost app upgrade -u https://github.com/user/someapp_ynh app_name
|
||||||
```
|
```
|
||||||
|
|
||||||
## Les services
|
## Les services
|
||||||
|
@ -65,7 +66,7 @@ YunoHost utilise toute une série de logiciels pour fonctionner. La plupart de c
|
||||||
Quand quelque chose ne fonctionne pas, une des premières choses à faire est de vérifier que tous les services utilisés par YunoHost sont lancés.
|
Quand quelque chose ne fonctionne pas, une des premières choses à faire est de vérifier que tous les services utilisés par YunoHost sont lancés.
|
||||||
YunoHost inclus un outil qui permet de visualiser tous les services utilisés par YunoHost :
|
YunoHost inclus un outil qui permet de visualiser tous les services utilisés par YunoHost :
|
||||||
```bash
|
```bash
|
||||||
sudo yunohost service status
|
yunohost service status
|
||||||
```
|
```
|
||||||
Exemple de résultat :
|
Exemple de résultat :
|
||||||
|
|
||||||
|
|
|
@ -44,7 +44,7 @@ vagrant ssh
|
||||||
|
|
||||||
Upgrade the system
|
Upgrade the system
|
||||||
```bash
|
```bash
|
||||||
sudo apt-get update && sudo apt-get dist-upgrade
|
apt update && apt dist-upgrade
|
||||||
```
|
```
|
||||||
|
|
||||||
You can access to your vm with the ip 192.168.33.10
|
You can access to your vm with the ip 192.168.33.10
|
||||||
|
|
|
@ -44,7 +44,7 @@ vagrant ssh
|
||||||
|
|
||||||
Mettre à jour le système.
|
Mettre à jour le système.
|
||||||
```bash
|
```bash
|
||||||
sudo apt-get update && sudo apt-get dist-upgrade
|
apt update && apt dist-upgrade
|
||||||
```
|
```
|
||||||
|
|
||||||
Vous pouvez accéder à votre vm via l’ip 192.168.33.10.
|
Vous pouvez accéder à votre vm via l’ip 192.168.33.10.
|
||||||
|
|
Loading…
Reference in a new issue