Install MariaDB

MariaDB is a MySQL compliant database that is a fork of the MySQL project. With MariaDB installed on a server, the server can use software that requires MySQL, as most of the popular web applications do. The installation of MariaDB in this article assumes a server running Ubuntu 16.04, nginx, and PHP with SSL/TLS installed as per the previous articles.

Most everything in this article will require root privileges.

username@servername:~$ sudo -i

Install and configure MariaDB
MariaDB 10.1 will be supported until October, 2020, making it a good candidate for admins desiring to perform minimal version upgrades but will be migrating from Ubuntu 16.04 to Ubuntu 20.04. MariaDB 10.1 is not in the official Ubuntu 16.04 repositories, so the MariaDB repository must be added.

root@servername:~# apt-key adv --recv-keys --keyserver hkp://keyserver.ubuntu.com:80 0xF1656F24C74CD1D8 root@servername:~# add-apt-repository 'deb [arch=amd64] http://ftp.osuosl.org/pub/mariadb/repo/10.1/ubuntu xenial main' root@servername:~# aptitude update && aptitude upgrade root@servername:~# aptitude install mariadb-server php5.6-mysql

The installation of MariaDB will require creation of a root database user password. The root database user will have full access to all databases stored on the server, while each application's database will have its own user created as part of the installation of the application. It is important to have a complex password for this user, though it will be needed to create new users and databases and perform other administrative tasks.

Configuration
Configure MariaDB to use Unix sockets.

root@servername:~# nano /etc/mysql/my.cnf

Add at the bottom:

Post Unix socket configuration to PHP:

root@username:~# nano /etc/php5/fpm/php.ini

Change:

Restart MariaDB and PHP.

root@username:~# service mysql restart root@username:~# service php5-fpm restart

Verification
To confirm MariaDB has been installed correctly, load the  page into a browser. PHP should now include two new blocks, mysql and mysqli.

Managing databases
Probably the most common method for database management is with phpMyAdmin. However, there is a command line tool for MariaDB that is usually faster than logging in to phpMyAdmin.

Common database usage
There are a number of practices that are commonly done, though not required, including using separate databases for each program installed that requires a database. Using one database and having different prefixes in each entry is simply not necessary and actually adds complexity to database management, as well as creating a single point of failure for several programs. This can occur if the table gets corrupted, which happens, or if one of the programs using the database is compromised.

Creating a common database prefix based on domains can also be useful. When performing maintenance on databases or backing up databases, phpMyAdmin can be a useful tool, and the phpMyAdmin Graphical User Interface (GUI) will conveniently group together databases that have the same prefix. If several domains run the same software, such as Piwik and are named 'piwik_domain', then they will all be grouped under 'piwik'. However, it may be more convenient to group databases by domain, and abbreviating the domain may be easiest. The domain example.com could be abbrevated 'ex', such that each database uses the suffix 'ex_', so 'ex_piwik', 'ex_wordpress', 'ex_smf', etc., would all be grouped together. It is also a good idea to use the name of the software. It may be that a domain will have multiple programs of one type of software, especially for testing purposes. Thus, instead of using 'ex_forum', using 'ex_vanilla' would be more practical.

Each database will have its own user with privileges only to edit the database the user is assigned to. It is common practice for the name of the database and its assigned user to share the same name.

Command line
The command line tool for MariaDB is identical to the one for MySQL, and is very powerful. This guide only explains the very, very basics of its use, as creating a database from command line is usually faster than logging into phpMyAdmin.

Logging in
The command line tool is accessed with the following command and then entering the MySQL root user's password: root@servername:~# mysql -uroot -p Enter password: Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 524 Server version: 5.5.32-MariaDB-1~precise-log mariadb.org binary distribution Copyright (c) 2000, 2013, Oracle, Monty Program Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [(none)]>

Create a new database
A database with UTF8, the type most commonly used, can be created with the following command: MariaDB [(none)]> create database databasename default character set utf8 default collate utf8_general_ci;

A user, user permissions, and user password can be assigned to  with the following command: MariaDB [(none)]> grant all on databasename.* to 'databasenameusername'@'localhost' identified by 'databasenameusernamepassword';

To exit the tool: MariaDB [(none)]> exit

phpMyAdmin
A popular GUI for MySQL compatible databases is phpMyAdmin, which allows for managing databases through a web interface. PhpMyAdmin can be installed through a PPA or as a regular PHP application. It is not advised to use the version of phpMyAdmin in the Ubuntu Precise repositories as it does not appear to be maintained. Using phpMyAdmin does not require a custom configuration, as it can be used as simply a PHP interface with MySQL. However, there are considerable features available for phpMyAdmin, which some administrators may desire. See the phpMyAdmin home page for information on custom configurations.

Configure sites-available file
PhpMyAdmin should only be opened in secure sessions, so a location block should be created to forward browsers to a secure session.

Create the  files:

root@servername:~# nano /etc/nginx/package-configs/phpmyadmin.conf

Add to the new file:

root@servername:~# nano /etc/nginx/package-configs/phpmyadmin_https.conf

Add to the new file:

PhpMyAdmin presents a nearly endless wellspring of  files that require to be passed. Fortunately, it is generally good at informing users when an error has been encountered, so be sure to check the error logs when some part of the installation appears to be failing for no other reason, and add to the above (alphabetical) list, as necessary.

It is important to note that due to the immense popularity of phpMyAdmin, there are a substantial number of bots scanning for vulnerable installations. It is a good idea to completely rename the directory containing phpMyAdmin, which, itself is not concerned with its directory name, other than the nginx permissions be properly configured. Simply replacing the  install directory location in the above and following instructions with any random name is enough to, at the very least, make a small dent in reducing server load, but note that it is not necessary to change the   file name.

root@servername:~# nano /etc/nginx/sites-available/example.com

Add to the HTTP server block:

Add to the HTTPS server block:

Test and reload nginx.

root@servername:~# nginx -t nginx: the configuration file /etc/nginx/nginx.conf syntax is ok nginx: configuration file /etc/nginx/nginx.conf test is successful root@servername:~# service nginx reload * Reloading nginx configuration nginx                                  [ OK ]

Install phpMyAdmin from zip file
The current version can be verified by checking the [//www.phpmyadmin.net/downloads/ phpMyAdmin Downloads page]. Since the installation steps are largely the same as the upgrade steps, they are presented as a normal user session. If in a  session, then changing ownership to   is not necessary. Download, decompress, and install phpMyAdmin:

user@servername:~$ wget --no-check-certificate https://files.phpmyadmin.net/phpMyAdmin/4.5.3.1/phpMyAdmin-4.5.3.1-all-languages.zip user@servername:~$ unzip -d /var/www/example.com/public/ phpMyAdmin-4.5.3.1-all-languages.zip user@servername:~$ rm phpMyAdmin-4.5.3.1-all-languages.zip user@servername:~$ mv /var/www/example.com/public/phpMyAdmin-4.5.3.1-all-languages/ /var/www/example.com/public/phpmyadmin user@servername:~$ find /var/www/example.com/public/phpmyadmin/ -type d | xargs chmod 775 user@servername:~$ find /var/www/example.com/public/phpmyadmin/ -type f | xargs chmod 664 user@servername:~$ sudo chown -R root /var/www/example.com/public/phpmyadmin/ The  is invoked because   does not support SNI.

The  file can optionally be created to provide a minimal feature set for phpMyAdmin. A sample file can be created with the built-in tool located at  https://www.example.com/phpmyadmin/setup/ .

user@servername:~$ nano /var/www/example.com/public/phpmyadmin/config.inc.php

Here is a sample file with some basic settings. The  option is the same as   covered above, but can only be viewed by users who are logged into phpMyAdmin.

Adding a long string of random characters into the  option (add them between the   marks) will make the session cookies more secure.

To log into phpMyAdmin, navigate to  https://www.example.com/phpmyadmin/  and use any user configured in MariaDB. Note that since phpMyAdmin is only a GUI for MariaDB, the user will only be able to make the changes as its permissions permit.

UNPM server complete!
The UNPM server is now set up and ready to serve. A good first project is to install Piwik. Piwik is a powerful web-analytics software that can be used to track and generate reports on site visitors. Nearly all popular web applications have plugins for Piwik.