The utility need not be run as root, but it does use sudo internally and may request your sudo password.
The utility allows the administrator to specify the environment (with the e flag) in which to spin up the chapter site. It is recommend that deployments be tested in another environment before being deployed to production.
Be sure that you do not have a mysql
in your home dir. Drush is very clever about looking for db credentials
to use. Similarly for the custom utils script (which sometimes use
The utility uses the login-path flag for mysql commands and assumes that the login-path “root” provides root access to MySQL. If you haven’t set this up for your user on the server, run mysql_config_editor set -h localhost -G root -u root -p and supply the MySQL root user’s password when prompted.
If you haven’t set up Mysql Login Path for your user on the server:
mysql_config_editor set -h localhost -G prod -u root -p
...and supply the MySQL root user’s password when prompted. Then repeat this for each environment, changing the -G flag for each: prod, dev, and stage.