the rationale here is that we can have different sites on different
ports that will be generated at different times, so we will not be
able to generate a full config file for all ports in one pass

rename the vhost_config hook to apache_vhost_config host and create a apache_dir_config hook to add configuration to the platformwide apache configuration

include a basic .htacces configuration there, but still allow the .htaccess to override while i do some tests

See: #384972

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

Move the provision help to hosting, severely reducing code duplication and simplifying provision even further

new hook: provision_vhost_config, to add stuff to the apache config file for a given site, in the vhost context
backported from d5

Test if apache can be restarted during verify, and fix the documentation for the hostmaster mysql user (#336431)

#321942 (primarily) - working config file generation and synch command. Also cleaned up variables passed to the system so the site_ prefix is no longer used.

Include additional information about install profiles, such as the human friendly name and description