Tutorials/Shared Database/fr: Difference between revisions

From KDE UserBase Wiki
(Created page with "Il existe plusieurs applications de bureau pour KDE qui gèrent une sorte de base de données. Les plus populaires sont probablement '''Amarok''' le lecteur de musique, '''digiKam''' le gestionnaire de photos et '''Akonadi''' le cadre d'informations personnelles. Pour simplifier leur installation et limiter leurs besoins, chacun de ces programmes embarque sa propre base de données, utilisant dans la plupart des cas '''SQLite'''. Avoir de nombreuses bases de données dis...")
(Created page with "La seule base de données universellement supportée par ces programmes est '''MySQL''', c'est donc celle que nous utilisons bien. Elle est également très simple à configurer, soit en ligne de commande, soit avec des outils graphiques.")
Line 10: Line 10:
=== Serveur de base de données ===
=== Serveur de base de données ===


The only database universally supported in these programs is '''MySQL''', so this is what we well use. It is also very easy to configure, either by command-line or with graphics tools.
La seule base de données universellement supportée par ces programmes est '''MySQL''', c'est donc celle que nous utilisons bien. Elle est également très simple à configurer, soit en ligne de commande, soit avec des outils graphiques.


==== Installation ====
==== Installation ====

Revision as of 20:02, 23 May 2024

Base de données partagée

Il existe plusieurs applications de bureau pour KDE qui gèrent une sorte de base de données. Les plus populaires sont probablement Amarok le lecteur de musique, digiKam le gestionnaire de photos et Akonadi le cadre d'informations personnelles. Pour simplifier leur installation et limiter leurs besoins, chacun de ces programmes embarque sa propre base de données, utilisant dans la plupart des cas SQLite. Avoir de nombreuses bases de données distinctes crée une surcharge inutile et rend plus difficile la sauvegarde de vos données.

Serveur de base de données

La seule base de données universellement supportée par ces programmes est MySQL, c'est donc celle que nous utilisons bien. Elle est également très simple à configurer, soit en ligne de commande, soit avec des outils graphiques.

Installation

First, we have to install the mysql server. Linux users will probably want to install a package from their distribution, other can get it from their homepage. Instructions to start MySQL at boot are distribution-specific, but since MySQL is a popular package, they shouldn't be hard to find. During the installation, the installer will probably ask you for a root password. Choose a secure password for this and remember it, this account will not be used by the desktop applications but only for database administration.

Configuration

For the server configuration, this we will assume that your database server is not used over the network, contains no sensitive data, and that you trust your applications. If you plan to use this database for Akonadi data, it's best if you copy the configuration file from the Akonadi code repository, which can be downloaded at here. Make a copy of your existing /etc/mysql/my.cnf, then replace it with the downloaded file.

Warning

This file disables network access and user authentication. The latter means that any application from your computer can connect to it without a password. This makes configuration of programs easier, and is well-suited for the general desktop use case.


Creating the databases

The first thing we have to do once MySQL is installed and running is add a separate database for each program. I generally name them after the programs that use them. This can be done with either GUI administration tools, but since we only have to do it once it's probably faster to write a few commands:

$ mysql -u root -p

At the password prompt, type in the root password set when installing MySQL. Now we can start creating databases. For example, to create a database named 'amarok', type in this command:

mysql> create database amarok;

Amarok

Amarok requires very little configuration, but it doesn't provide a way to migrate your old database. Go to Settings -> Configure Amarok... and go to the Database tab. Fill in localhost in the Server textfield, 3306 in Port, and amarok in Database.

digiKam

Note

digiKam used to have a bug which prevented the same from working in versions prior to 2.0, so you will need a newer version of the program. In version 2.0 is still doesn't work perfectly: it pops up an error message at startup, but the tables are populated and the album data is stored correctly.

digiKam is somewhat special because it requires two databases: one for the images metadata, and one for thumbnails. Their names are not important, I chose to call them digikam and digikam_thumb:

mysql> create database digikam;
mysql> create database digikam_thumb;

In digiKam, the process is very similar to that of Amarok. The settings are located in Settings -> Configure digiKam... -> Database.

digiKam also comes with a handy database migration tool, available in Settings -> Database Migration. Fill in your previous database settings (you don't have to do anything if you haven't changed these options) on the left side and your new settings on the right side, then click Migrate.

Akonadi

First create a database for Akonadi:

mysql -u root -p
create database akonadi;

Akonadi is not supposed to be a user-facing tool, so there is no configuration GUI for it. However, you can edit ~/.config/akonadi/akonadiserverrc to have these contents:

[%General]
Driver=QMYSQL

[QMYSQL]
Name=akonadi
Host=localhost
StartServer=false
Options=
ServerPath=/usr/bin/mysqld

Save the file, then log out and log in back again.