MySQL Sandbox is a tool that offers a quick and painless install of side MySQL server in isolation.
It can help you to install one or more MySQL servers in isolation, without affecting other servers
Installation:
Unpack the necessary MySQL binaries somewhere under your home directory, and give it a convenient name (e.g. /opt/mysql/5.1.10, or $HOME/binaries/5.1.10 )
Unpack the distribution package in one empty directory and run the install script. For example:
$ ./install.pl -f sandbox.conf --basedir=$HOME/binaries/5.1.10
You can create the data directory in two ways:
- using mysql_install_db script. In this case, the sandbox will run an additional script to install username and password in the database.
install.pl --datadir_from=script
- copying from an already existing directory (you need to have the necessary privileges to read fies from the origin)
install.pl --datadir_from=dir:/usr/local/mysql/data/mysql
To see the available options, run ./install.pl --help
Usage:
Change directory to the newly created one (default:
$HOME/mysql_sandboxVERSION)
Start the server
./start.sh
Stop the server
./start.sh
use a client with the sandbox server:
./use.sh
Product's homepage
Requirements:
· Linux or FreeBSD operating system
· MySQL
· Perl
· Bash
What's New in This Release: [ read full changelog ]
· MySQL Sandbox 3.0.19 now supports tarballs that don't start with 'mysql'.
· Supported prefixes are 'mysql', 'percona', and 'mariadb'.
· You can also add a prefix to the extracted tarball directory.
· These changes have the side effect of making "make_sandbox" backward incompatible. The syntax goes from
· "make_sandbox TARBALL [--export_binaries] [options for low_level_make_sandbox]"
· to
· "make_sandbox [--export_binaries|--add_prefix] TARBALL -- [options for low_level_make_sandbox]"
· (notice the '--' before the final options)