We have decided that along with the move of drush_extras back into drush core, we will be adding the provision install and update commands, which offer full support for install profiles and languages.
Here are the related files :
Drupal 5
http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/provision/p...
http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/provision/p...
Drupal 6
http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/provision/p...
http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/provision/p...
Drupal 7
http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/provision/p...
http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/provision/p...
These files fully support the drush_logging and error handling API, making for very clean and very useful commands.
| Comment | File | Size | Author |
|---|---|---|---|
| #18 | autoinstall_drupal.txt | 1.09 KB | David_Rothstein |
Comments
Comment #1
bjaspan commentedsubscribe
Comment #2
swentel commentedThis will rock once this gets in .. subscribing so I can review patches later!
Comment #3
anarcat commentedI'm also go for this...
Comment #4
adrian commentedCommitted the provision update commands to HEAD.
install will come later.
Comment #5
adrian commentedComment #6
rsvelko commentedwhat about modules and themes - are they handled in the install.inc
(I know of drush dl and drush enable (that might be combined/used here) - but dl does not check for dependancies I suspect while enable does )
Comment #7
adrian commentedthis is for installing the entire site, using the install profile as the map of what modules to enable.
this is not for installing modules.
Comment #8
rsvelko commentedok, the second part of the question is whether the install command is going to install modules and themes one day?
Comment #9
adrian commentedYou are thinking of the 'dl' and 'enable' commands, and i believe they do. They even do translations.
The install command (at the moment) is a replacement for Drupal's install.php, and it fully supports install profiles and their related modules and themes.
Comment #10
adrian commentedThis is only scheduled for the next release after 2.0
Comment #11
moshe weitzman commentedOK, 2.0 is released. Lets tackle that pesky install command.
Comment #12
psynaptic commentedAhh, this is great. I just posted in another thread but this look like where it's all going down.
Anything you need help with, just let me know.
Comment #13
joachim commentedI'm keen to see this get into drush.
Any way I can help beyond testing eventual patches?
Comment #14
SeanBannister commented+1 Subscribe
Comment #15
Logi Khoo commentedFor my case, i'll write a shell script for copying/chmod default.settings.php.
An example of executing the script:
So... +1 for the install command!
Comment #16
meecect commentedsubscribe
Comment #17
David_Rothstein commentedNote that for Drupal 7, I just posted a patch at #524728: Refactor install.php to allow Drupal to be installed from the command line which, if it were to get in, would make the Drush command relatively trivial, and easy to maintain.
Comment #18
David_Rothstein commentedSince #524728: Refactor install.php to allow Drupal to be installed from the command line has been in for a little while, Moshe asked me if there was a rough installation script that could be used as a starting point for Drush.
Attached is what I've been using to install Drupal 7 on my local machine. The stuff in capital letters gives an idea of the things that Drush would need to allow the end user to customize (although really any of it could be customizable).
This script would change a bit once the followup cleanup patch to #524728: Refactor install.php to allow Drupal to be installed from the command line actually gets committed (hopefully soon), but actually not too much.
Comment #19
moshe weitzman commentedCommtted an initial version of this. Needs to smarten up in many ways (multisite, security, ...). Patches welcome.
Note that it requires a patch to core that is RTBC - #557542: Cache module_implements() . We also see 3 harmless, odd looking errors in drush logs which would be fixed by #325169: Move error/exception handler higher up in the bootstrap process