Différences
Ci-dessous, les différences entre deux révisions de la page.
Les deux révisions précédentes Révision précédente Prochaine révision | Révision précédente | ||
recherche:cis-projets [14/02/2024 11:54] – dberthet | recherche:cis-projets [12/03/2024 16:44] (Version actuelle) – [Logiciels installés post-installation] mancuso | ||
---|---|---|---|
Ligne 5: | Ligne 5: | ||
* **Chaque projet doit impérativement être accompagné de sa déclaration de traitement RGPD validée par le DPO** | * **Chaque projet doit impérativement être accompagné de sa déclaration de traitement RGPD validée par le DPO** | ||
+ | * // | ||
+ | ===== Logiciels installés post-installation ===== | ||
+ | * //Base de données// | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | Synchronizing state of mariadb.service with SysV service script with / | ||
+ | Executing: / | ||
+ | < | ||
+ | NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MariaDB | ||
+ | SERVERS IN PRODUCTION USE! PLEASE READ EACH STEP CAREFULLY! | ||
+ | In order to log into MariaDB to secure it, we'll need the current | ||
+ | password for the root user. If you've just installed MariaDB, and | ||
+ | haven' | ||
+ | |||
+ | Enter current password for root (enter for none): | ||
+ | OK, successfully used password, moving on... | ||
+ | |||
+ | Setting the root password or using the unix_socket ensures that nobody | ||
+ | can log into the MariaDB root user without the proper authorisation. | ||
+ | |||
+ | You already have your root account protected, so you can safely answer ' | ||
+ | |||
+ | Switch to unix_socket authentication [Y/n] n | ||
+ | ... skipping. | ||
+ | |||
+ | You already have your root account protected, so you can safely answer ' | ||
+ | |||
+ | Change the root password? [Y/n] Y | ||
+ | New password: | ||
+ | Re-enter new password: | ||
+ | Password updated successfully! | ||
+ | Reloading privilege tables.. | ||
+ | ... Success! | ||
+ | |||
+ | By default, a MariaDB installation has an anonymous user, allowing anyone | ||
+ | to log into MariaDB without having to have a user account created for | ||
+ | them. This is intended only for testing, and to make the installation | ||
+ | go a bit smoother. | ||
+ | production environment. | ||
+ | |||
+ | Remove anonymous users? [Y/n] Y | ||
+ | ... Success! | ||
+ | |||
+ | Normally, root should only be allowed to connect from ' | ||
+ | ensures that someone cannot guess at the root password from the network. | ||
+ | |||
+ | Disallow root login remotely? [Y/n] Y | ||
+ | ... Success! | ||
+ | |||
+ | By default, MariaDB comes with a database named ' | ||
+ | access. | ||
+ | before moving into a production environment. | ||
+ | |||
+ | Remove test database and access to it? [Y/n] Y | ||
+ | - Dropping test database... | ||
+ | ... Success! | ||
+ | - Removing privileges on test database... | ||
+ | ... Success! | ||
+ | |||
+ | Reloading the privilege tables will ensure that all changes made so far | ||
+ | will take effect immediately. | ||
+ | |||
+ | Reload privilege tables now? [Y/n] Y | ||
+ | ... Success! | ||
+ | |||
+ | Cleaning up... | ||
+ | |||
+ | All done! If you've completed all of the above steps, your MariaDB | ||
+ | installation should now be secure. | ||
+ | |||
+ | Thanks for using MariaDB! | ||
+ | </ | ||
+ | |||
+ | * //Contener Docker// | ||
+ | https:// | ||
+ | 1-Set up Docker' | ||
+ | < | ||
+ | # Add Docker' | ||
+ | $ sudo apt-get update | ||
+ | $ sudo apt-get install ca-certificates curl | ||
+ | # $ sudo install -m 0755 -d / | ||
+ | $ sudo curl -fsSL https:// | ||
+ | $ sudo chmod a+r / | ||
+ | |||
+ | # Add the repository to Apt sources: | ||
+ | echo \ | ||
+ | "deb [arch=$(dpkg --print-architecture) signed-by=/ | ||
+ | $(. / | ||
+ | sudo tee / | ||
+ | sudo apt-get update | ||
+ | </ | ||
+ | |||
+ | 2-Install the Docker packages. | ||
+ | To install the latest version, run: | ||
+ | < | ||
+ | |||
+ | 3-Verify that the installation is successful by running the hello-world image: | ||
+ | < | ||
+ | Hello from Docker! | ||
+ | This message shows that your installation appears to be working correctly.</ | ||
+ | |||
+ | * // | ||
+ | < | ||
+ | |||
+ | < | ||
+ | * Mot de passe défini par Riviere. | ||
+ | * création rep docker pour les fichiers compose et données registry | ||
+ | < | ||
+ | cis-lab: ~ # chown -R docker: / | ||
+ | </ | ||
+ | * création rep docker pour fichiers statiques générés par les dockers. | ||
+ | < | ||
+ | cis-lab: ~ # chown -R docker: / | ||
+ | < | ||
+ | cis-lab: ~ #/ | ||
+ | </ | ||
+ | * //editer nginx.conf pour configuration nginx lancé par les dockers // | ||
+ | * //ajout ligne : include / |