GitLab

#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

The hostmaster platform will be automatically downloaded by hostmaster migrate if the target platform does not exist yet

Rename the park/unpark commands to pause/resume, due to incorrect validation in the hosting park component in 0.4 alpha 2 which would cause all migrations to fail

During deploy, updatedb is run in a backend process on the OLD database because the new database details have not been saved to the drushrc yet, which is now the canonical source for the information

add publish_path to the list of variables that need to be overridden, and use a more sensible rollback mechanism.

Add a confirmation to the hostmaster migrate command and wipe out the crontab so that the dispatcher is no longer invoked

Abstracted the functionality to prepare the $_SERVER variable into provision_prepare_environment() and additionally fix migrations

Small fix to how the site configuration is saved and also preload the $_SERVER variable during install task

Use apaches mod_env to set the database credentials in the virtualhost file, so that they are only accessible inside a specific process. the $_SERVER values are now bootstrapped in the verify site process and the config file rewritten, so that you can now safely verify a site. the $_SERVER values are stored inside the site drushrc.php so that normal drush commands will continue to operate as they would. The open_basedir directive is commented out until we can resolve issues with it.

this also makes sure that ~/config/includes/global.inc exists so that open_basedir checks don't break

this is just a quick workaround to make sure sites can't access the aegir site database, which should be kept in a separate platform

Spotted and original patch by: emspace

#613302 - slight validation change so that schema version in current release is used when schema version in target release not defined

Revert "workaround for #485646 - pass the commandline arguments for the DB to deploy so we can force the database server manually"

This makes the *master* password show up on the commandline. Bad. We'll need to find another way.

This reverts commit 0eb09b06887129160ac0ea5ac555e35c45cb8d46.

include the time in the backup file so we know when the backup was done, regardless of the timestamp

workaround for #485646 - pass the commandline arguments for the DB to deploy so we can force the database server manually

this improves performance radically on big backups

'could not connect to the master database server' as opposed to just 'could not connect to the master database' which doesn't make sense here