To clarify, CustomBuild 2.0 can use whatever is already installed.
The related option is one of:
Code:
mysql_inst=yes
mysql_inst=mysql
mysql_inst=mariadb
where "yes" would use whatever is already installed, based on:
Code:
mysqld -V | grep -c 'MariaDB'
Else, if you use mysql_inst=mysql, it will try and only use mysql (it will error if you have the wrong thing installed). Similiar, you can set it to mysql_inst=mariadb if you only want that.
Really, using "yes" should be all you ever need, as long as you've got what you want already installed.
This means, if you want MySQL, swap out MariaDB for MySQL, and CB2.0 should continue to work with it, allowing you to update to 5.6.
But.. once you go to 5.6, you're locked in (unless you dump the raw sql, wipe the db path & rpms, and re-install to MariaDB).
Same for MariaDB 10.. once you have that, you can't go back to MySQL 5.6, unless you do the full dump/delete/install/restore.
I too was quite leery of MariaDB, as change causes confusion and breaks things. I'm typically hesitant to do so.
However, after I did a bit of digging and testing, I found to have no issues at all and that MariaDB is actually more "MySQL" (historically) than the new MySQL is.
What I mean by that is, MariaDB
is MySQL, and is developed by the original MySQL creators.
MySQL was bought by Oracle, so from 5.6+, it's not developed by the original MySQL team, which is why everyone seems to be moving away from it (I'm sure it's fine, but it's a new team of coders)
So in reality, if you want consistency, oddly enough, using MariaDB would be that path, as it
is the original MySQL 5.5 code base, and worked on by the
original MySQL developers, and MariaDB 10
would have been the natural increment of MySQL, if it were still owned by the same people.
The only thing different is the name.
I would personally be more suspicious of MySQL 5.6, than I would be of MariaDB 10.
In any case, it's not 100% ironed out on how we'll do it, but right now, CentOS 7 will install MariaDB.
If you want MySQL, simply swap out the MariaDB 5.5.x rpms, with the MySQL 5.5.x rpms (as they're essentially the same thing).
Then if you want to move to MySQL 5.6, you can do so normally.
The quick solution to swap MariaDB to MySQL after the CentOS 7 install is done:
Code:
cd /root
mkdir mysql
cd mysql
wget http://files.directadmin.com/services/all/mysql/64-bit/5.5.40/MySQL-client-5.5.40-1.linux2.6.x86_64.rpm
wget http://files.directadmin.com/services/all/mysql/64-bit/5.5.40/MySQL-devel-5.5.40-1.linux2.6.x86_64.rpm
wget http://files.directadmin.com/services/all/mysql/64-bit/5.5.40/MySQL-server-5.5.40-1.linux2.6.x86_64.rpm
wget http://files.directadmin.com/services/all/mysql/64-bit/5.5.40/MySQL-shared-5.5.40-1.linux2.6.x86_64.rpm
rpm -e `rpm -qa | grep MariaDB`
rpm -Uvh MySQL*.rpm
and you should be up and running.
Be sure you do this as soon as the install is done, just to be sure.
Again 5.5 for MySQL and MariaDB should be the same, so you can in theory do it later, but better sooner than later.
John
Only 5.5 is available for now in CB 2.0.
. Perhaps I'll post on WHT to see what ordinary users look for and to see what other hosting companies are doing, but a quick search right now shows: