X-Git-Url: https://git.ao2.it/drupal-init-tools.git/blobdiff_plain/cce156e037cf0e04db479c4eea768c0a933ae4b2..f4f92c2b7ddb36cda3da9a529a3118ee06455be4:/drin.rst?ds=inline

diff --git a/drin.rst b/drin.rst
index ed21253..becb8c3 100644
--- a/drin.rst
+++ b/drin.rst
@@ -22,12 +22,14 @@ DESCRIPTION
 
 Helper commands to create and install new Drupal projects.
 
-When setting up a new Drupal project with drupal-composer/drupal-project drush
-and drupal-console are not available yet and some repetitive tasks can use
-a nicer command line interface.
+One problem with setting up a new Drupal project with
+drupal-composer/drupal-project is that drush and drupal-console are not
+available until the site dependencies have been downloaded, drupal-init-tools
+helps to solve this and also adds a nicer command line interface to some
+repetitive tasks.
 
-These scripts are especially useful when setting up projects in user web
-directories[1].
+drupal-init-tools commands are especially useful when setting up projects in
+user web directories[1].
 
 [1] http://httpd.apache.org/docs/current/howto/public_html.html
 
@@ -46,7 +48,7 @@ Available sub-commands:
   ``new`` `[-h|--help]` `<destdir>` `[composer options (e.g. --devel)]`
     Create a new Drupal project in the `destdir` directory.
 
-  ``bootstrap`` `[--devel|-h|--help]"`
+  ``bootstrap`` `[--devel|--overwrite-profile|-h|--help]`
     Bootstrap a Drupal project, using settings from a `bootstrap.conf` file.
 
   ``clean`` `[-h|--help]`
@@ -84,6 +86,41 @@ Clean and rebuild the whole project to verify that installing from scratch works
   drin clean
   drin bootstrap
 
+NOTES ON DATABASE SETUP
+=======================
+
+The `bootstrap` command in `drupal-init-tools` uses `drush` for the site
+installation, and `drush` requires MySQL super-user access to create new MySQL
+users and databases.
+
+On some Linux distributions, like Debian, the MariaDB server is configured by
+default to only allow access to the `root` user via the `unix_socket` plugin,
+making it unusable by `drush`. In these cases it's recommended to create e new
+MySQL super-user.
+
+For password-less access create a MySQL admin user correspondent to the system
+user which will execute `drush` (e.g. the current user):
+
+::
+
+  sudo /usr/bin/mysql -e "GRANT ALL ON *.* TO '$USER'@'localhost' IDENTIFIED VIA unix_socket WITH GRANT OPTION"
+
+
+For password regulated access create a user with a password:
+
+::
+
+  sudo /usr/bin/mysql -e "GRANT ALL ON *.* TO 'USERNAME'@'localhost' IDENTIFIED BY 'password' WITH GRANT OPTION"
+
+
+For details see also the **PASSWORDS** section in the README.Debian file
+provided by the mariadb-server Debian package, either in
+`/usr/share/doc/mariadb-server-10.1/README.Debian.gz` or at 
+https://salsa.debian.org/mariadb-team/mariadb-10.1/blob/stretch/debian/mariadb-server-10.1.README.Debian#L73
+
+The settings in the `bootstrap.conf` file have to be adjusted according to how
+super-user access has been configured.
+
 
 SEE ALSO
 ========