GitLab

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

Simplify verify code by creating _provision_create_dir function. Removed duplicate code from other modules. Need this in hosting_setup too.

Significantly improved the requirement checking and contextual help. All this stuff is integrated into the wizard, and eventually will add queues from provision to hosting to flag exact errors. Introduce some simple jquery and css to handle collapsible and collapsed help text, to clean up the pages a bit

Finishing splitting up help into _requirements() functions, and fix the web_group validation to work with the new wizard forms

Refactor the help code a bit, by adding a _provision_requirements function, which calls _provision_$req_requirements() functions, containing the actual help text. Allows me to much more easily integrate help text into forms. Also added some weights to the db_server and web_server forms, so that they can be more easily manipulated

Missing return to db create function. Added additional error checking. Become more stringent about regenerating the config files. Wrong path to database.sql

#245664 - add validation to check that user is in the correct group during provision configuration. updated help text with howto on configuring the user group.

Added restore functionality for #237555. Implement rollback as well, if something goes wrong it rolls back to the initial system status

More work towards restore functionality. Moved the mysql utility functions to provision_mysql.inc, and the help stuff to it's own include too.

Made more constants to replace the various helper functions, still need to document them.

Replaced all references to db_username with db_user, which is consistent with everywhere else in the system.

It is now called provision_path, and instead of the nasty switch statement it has a small set of pluggable  functions, which work similarly to theme() etc. For that reason I also ended up changing the order of the parameters to be provision_path('mkdir', 'somepath').

The functionality grew to over 200 lines of code (mostly comments), so i split it off into it's own file.

I also added checks that the user is in the correct group, and it will specify it to the user if it comes to it, but I should really hook it up into the user interface and write some better documentation about it before i can close #245664. Although it seems chgrp now fails silently for me, even from the command line. Please check it out.

I moved _provision_drupal_recursive_delete to provision.inc and removed the drupal from the module prefix. I also made it use the provision_path module for logging purposes, cleaning it up a bit.

#262008 is now completely fixed. I've re-added the permission checking in provision_drupal.module, since it now works. It was missing a clearstatcache(), so i added these pretty liberally.

Part of the fallout from this, is that each of the provision_path_ functions have an optional third parameter, which is a reference. This reference can be used to provide a reason for the operation failing. Also, mostly due to the chown function, i run the messages through t() before they get sent to logs. Meaning developers can just use @path and @confirm in their error messages, and they get the centrally prettied up variables. It's made the verify code a lot easier on the eyes. just check out provision_verify.

Added redirection to a new site maintenance page, for while the site is being restored.

Added a switch paths function, which flips around site directories. I'm building restore to be non-destructive, until after the site has been completely restored and verfied. #237555

I'm making a move to using more defines for various site infrastructure things. I just tackled the paths, will do the current user and current group stuff soon, bringing it back in line with hosting. It cleared up a fair amount of code just doing the paths.

See #259383

make a 'this site is disabled' page target. people can override this by changing the provision_apache_disabled_url variable (no visible ui for that yet). See #259383

just removing the config file will not work since the default vhost kicks in and still allows the disabled site to work. instead, we
create a custom vhost configuration file that redirects to a "disabled" url (that we should make configurable eventually).

right now that url is just $base_url/disabled, which gives a page not found, but i'll work more on that