GitLab

drush_get_error()

set the settings.php group based on the web_group defined on the platform args instead of the predefined default group

this is required for the ITK extensions

See: #334416

try harder to set the permissions in provision_path_chgrp(), because unknown groups may come through with the ITK extensions

See: #334416

Provide a layer of conditional includes for specific Drupal versions. One provision install can now drive Drupal 5, 6 and 7 platforms, without needing anything additional downloaded.

Added migrate command. Can no go drush.php provision migrate somesite.com /path/to/other/platform, and it will re-deploy it on the new platform, cleaning up after itself. with full rollback. It will also run any outstanding updates, which means we now (theoretically) have both major and minor version upgrades. What is missing is version checking to ensure you are not deploying on a platform with missing packages etc.

Fix update command, is now called during deploy. Provision can now upgrade between minor versions and major versions. Still missing migrate command

Synched head with d6 branch. Works with drush 2.x and no longer needs to be enabled on a site, as it is no longer a module. Hosting has not been updated to point to the right place per server, so you have to create the symlink to the central drush.php yourself. I have not sorted out the version specific stuff yet either.

First import of the basis of the 0.2 release of provision. This version has a much cleaner api, through the dynamic inclusion of <command>.provision.inc files , which any module can overload. Each of these files has the exact same structure, and thus it is much clearer what happens when, and much much simpler to document / extend. I also removed all the drupal dependencies i could find, in preperation for moving to a version agnostic drush, for all buy provision_drupal (which is going to be spun off into a different project). This also includes a working update command, and keeps track of the modules installed on a site after every verify / upgrade process. This information is not being tracked in hosting, yet

Experimental update.php for DRUPAL 6. This is not integrated into any drush commands or the hosting front end yet