because of #955018, setting site_offline doesn't propagate to the context so we need to use a variable already defined, we chose site_enabled

because of #955018, setting site_offline doesn't propagate to the context so we need to use a variable already defined, we chose site_enabled

A bevy of subtle fixes. Primarily #597750 because we no longer 'do' site id. Also fixed restore which left you with a broken site, and handled the fact that
the drush_config_file function would only give us the right value when we were bootstrapped to that level.

this meant we couldnt regenerate the site drushrc.php until we'd bootstrapped to drupal_configuration, which meant during restore it would always use the old values.

Also when the restore task finished, the save_site_config malarky would end up writing the old values over the correct ones.

the singular filesystem object now.

Sync is now a method of the server class, with a helpful method associated
to the services that redirect to the service's server.

Sort of fix site import, which also verifies now. Introduce d()->site_path instead of concatenating everywhere.

Removed the provision_service function, and introduce service handler subscriptions in the environment objects.

Instead of provision_service('type') you now use d()->service('type') to access the service object.
The context object returned by d() now manages which context object's service to return, based
on the internally managed subscriptions.

Committed drumm's cleanup patch that takes care of permission checks inside the config writing code,
and some other fixes to get install etc. working again

This gets rid of the path function, and introduces method chaining for the file service, which results in far cleaner code.

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

#456622 - ensure that drush_invoke operates in a clean namespace and does not mistake drupal hooks as its own. Check the issue for the conversion script.

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