Rules as stored in the database in the column code like this:

file.name = 'yum/'

file.title = 'Red Hat, Fedora, and CentOS Packages'

file.file_type = 'rpm'

file.cpu = 'blank'

release_status = 'stable'

file.os = 'rhel_centos_fedora'

file.size = None

file.blurb = 'For best results with RPM packages, use the [[https://downloads.mariadb.org/mariadb/repositories/|Repository Configuration Tool]].'

file.name = 'repo/'

file.title = 'Debian and Ubuntu Packages'

file.file_type = 'deb'

file.cpu = 'blank'

file.os = 'debian_ubuntu'

release_status = 'stable'

file.size = None

file.blurb = 'For best results with DEB packages, use the [[https://downloads.mariadb.org/mariadb/repositories/|Repository Configuration Tool]].'

The Files table uses 2 columns to displays its files on the website: first is Name and second is Title.

The rules are used to populate the Title column in the Files table. The Title column is used instead of the Name column to display a certain file or set of files. For example: for yum/ or repo/, the servers uses the Titles for the files instead of the Name in the web page : 'Red Hat, Fedora, and CentOS Packages' (yum/) and 'Debian and Ubuntu Packages' (repo/).

The problem appears when a lot of the files have the Title column NULL in the database (because they use the Name column to be displayed such as: mariadb-connector-nodejs-2.3.1.zip.

A possible solution is to have the Title column populated for all entries and be the one used when displaying files on the website.