Drupal 10, the latest version of the open-source digital experience platform with even more features, is here.The module for quickly reinstalling a site seems like a good candidate for hosting_task_extras.
3.x version is in https://www.drupal.org/project/hosting_dev
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | add_hosting_site-2838431-7.patch | 4.04 KB | helmo |
| #6 | 2838431-add-reinstall.patch | 3.8 KB | Jon Pugh |











Comments
Comment #2
Jon PughComment #3
Jon PughPatch attached. I don't have commit access to push a branch.
Comment #4
Jon PughComment #5
Jon PughComment #6
Jon PughComment #7
helmo CreditAttribution: helmo at Initfour websolutions for Aegir Cooperative commentedI added a warning to the confirmation form...
When testing I got one warning:
In provision/platform/install.provision.inc we pass in the client_email ...
Which we don't in this code:
I don't think we get this option in the current context, but we should be able to...
Comment #8
helmo CreditAttribution: helmo at Initfour websolutions for Aegir Cooperative commented@Jon Pugh now you do have maintainer access
Comment #9
Jon PughYeah, for some reason client_email is not a property on the site context...
Wouldn't it make sense to do that so we don't have to pass it all the time?
Comment #10
helmo CreditAttribution: helmo at Initfour websolutions for Aegir Cooperative commentedI guess that the original thought was that it would be only needed once... during install.
But the value originates in the client... so in the site context it would be a copy, which needs to be kept in sync :(
Comment #12
Jon PughHelmo: I pushed the patch into a new branch: 2838431-reinstall
Here's the code that sets the client_email:
From hosting/site/hosting_site.drush.inc
I think we can go ahead and assume that the Site UID is the intended client. If someone changes the author of the site, they are doing se advanced stuff as we block those fields, right?
I'll push a patch to set these in the reinstall task.
Comment #13
Jon PughI'm not sure anymore we need a new task type.
The "install" task can be forced to run again instead. We could alter the install task confirm form to provide a good user experience, and plenty of warning that the site will be destroyed.