-
Notifications
You must be signed in to change notification settings - Fork 153
installation
[HOME]
The installation is simple, as the only thing you will need is a binary executable for your operating system. Get the one for your O.S. from dbdeployer releases and place it in a directory in your $PATH. (There are no binaries for Windows. See the features list for more info.)
For example:
$ VERSION=1.56.0
$ OS=linux
$ origin=https://github.com/datacharmer/dbdeployer/releases/download/v$VERSION
$ wget $origin/dbdeployer-$VERSION.$OS.tar.gz
$ tar -xzf dbdeployer-$VERSION.$OS.tar.gz
$ chmod +x dbdeployer-$VERSION.$OS
$ sudo mv dbdeployer-$VERSION.$OS /usr/local/bin/dbdeployer
Of course, there are prerequisites: your machine must be able to run the MySQL server. Be aware that version 5.5 and higher require some libraries that are not installed by default in all flavors of Linux (libnuma, libaio.)
As of version 1.40.0, dbdeployer tries to detect whether the host has the necessary libraries installed. When missing libraries are detected, the deployment fails with an error showing the missing pieces. For example:
# dbdeployer deploy single 5.7
# 5.7 => 5.7.27
error while filling the sandbox definition: missing libraries will prevent MySQL from deploying correctly
client (/root/opt/mysql/5.7.27/bin/mysql): [ libncurses.so.5 => not found libtinfo.so.5 => not found]
server (/root/opt/mysql/5.7.27/bin/mysqld): [ libaio.so.1 => not found libnuma.so.1 => not found]
global: [libaio libnuma]
Use --skip-library-check to skip this check
If you use --skip-library-check
, the above check won't be performed, and the deployment may fail and leave you with an incomplete sandbox.
Skipping the check may be justified when deploying a very old version of MySQL (4.1, 5.0, 5.1)