GitLab

L10n support for install profiles. Detects and installs sites using the available languages correctly. Does not currently detect the language of installed sites correctly. Will fix this along with #319299 momentarily

Almost installs profiles now, but there is a major problem creating sites that have the views module in the profile, as there is a code conflict

Rollback an error in the previous patch that broke installation of new sites. Throw an error if the modules for an install profile arent found

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

Ensure that including settings.php from imported sites, to get their settings, to not modify the php ini_set environment

I managed to never commit the provision.install file, which sets the module weights, and makes sure that restore happens in the right order.
This fixes the problem I had where it would try to import the database dump before actually having extracted it.
Fixed the weird chgrp error message it was having (which was just an issue in logging, not in the actual chgrp call)

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

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

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

temporarily disable chown error flag on sites directory creation. the permissions are being correctly set, but the tests are failing

fix the name of the user/group variables: it's now provision_script_user and provision_web_group, to follow what is configured in hosting

now this works, but the hostmaster user (or the script running the cron job) needs to be part of the provision_web_group

Site creation is working again. There was a bug in the db switching code, and some permission changes that i commented out for now while i am testing

this fixes a few warnings

In progress commit. Remove dependency on date module. Lots of help additions. Added verify step so the back end (mostly) configures itself. Switched templating to use php instead of tokens (needed loops in templates). Turned options to use underscore instead of dash for separation (now consistent). Lots of validation and logging, including strict permission checking.

refactored database_mysql, added helper functions for finding out group name and file owner name. added functionality to stop functions from being run via the web. slightly updated documentation

Initial import of provisioning framework into drupal contrib. This set of modules extends Drush to provide the ability to install and manage Drupal sites. It is the back end component of the hostmaster system.