GitLab

this was failing because provision_path_unlink was checking the file existence (file_exists) before removing the symlink. in this case, the file really *didn't* exist because the link target was already removed.

instead of checking, we just try to delete the file, if it fails, it will return false anyways.

we do the same with rmdir while we're here.

also make sure we work on the trimmed file path

The init and exit hooks were expecting to only be running on "provision *" commands, i modified them to run on "provision-*" commands instead.

changed all instances of drush_backend_invoke and drush_invoke to match
the new command names.

valid

first, it's not necessarily available. second, we have proper failure
modes anyways, so this check isn't useful

this way we can have the "aegir mysql root" user to be a bit more
restricted in his actions

Revert "initialize mysql credentials from drush bootstrap so that we can work on non-verified sites easily"

Provision is managing the master database connection here, drush's db credentials are the details for the SITE, and will only be available at drush_bootstrap_drupal_site.

we need the master db connection from drush_bootstrap_drush already, and we will never ever ever be able to make use of drush' code in this regard because what we are doing is completely outside of the Drupal context.

This reverts commit 5439e6d01d32fd7351c404a6bf74c11a028ee8a4.

raise backup bootstrap level to configuration so we load the settings file and therefore be able to backup existing, non-verified sites for easier import into aegir

we do it the proper way, by using site_exists(), not site_installed()

This breaks site creation: the site_id and other parameters are no
longuer saved in the drushrc after this patch is applied.

This reverts commit 5e9df86344397f47030e31840e14fb3c93c69b11.

change variable names to be more consequential, better docs of _provision_drupal_create_directories()

#536100 by anarcat - add libraries folder to sites/all and sites/. see http://drupal.org/node/496240

Do not create the platform_.conf file if no platform ID is present. this resolves the last minor issue with the upgrade path

files url stay consistent across site renames and clones