Posted by ckosloff on May 8, 2014 at 6:21pm
I have read through the article at omega8.cc, watched videos, checked project drush make documentation (very outdated, superseded by drush), and still unclear how to create platforms.
Please don't tell me they go under ~/static or permissions, I know that.
Can somebody give me simple steps to create custom platform for latest Drupal 7.28?
Comments
My notes are here.
My notes are here.
SUCCESS
Thank you very much for the head start.
Platform creation was successful.
Now to answer this question in your notes:
(foo permission should be 775 ??)
Answer is yes, next I quote omega8.cc article on making platforms.
"Now, the only thing you should remember about is to set group writable permissions for platform’s root directory, plus its sites and core modules subdirectories, so something like: chmod 775 ~/static/foo-bar plus chmod -R 775 ~/static/foo-bar/sites and chmod 775 ~/static/foo-bar/modules. You must set this chmod before adding the platform in the Aegir interface, or it will yell with errors or cause warnings later."
So I completed that first step, called platform d728.
For the second step I navigated as root to the root of an existing Drupal installation to create the make file.
But upon running the command, drush started yelling that it should never be run as root, so switching to user o1 is previous to this step.
All the rest is good, if perms were set to 755 in step 1, then the first is not needed, it will say that perms were retained as 775, the second line is necessary since subdirectory sites did not exist previously.
Some comments:
I only installed core, so my demo.make is practically a one-liner.
I saw no .info file where to change names to vanilla standard, etc. as omega8 article indicates.
Even though I only installed core I saw lots of extraneous modules like Advagg, ESI-x, mPDF library handler and several others.
I don't know if that is caused because I missed this step:
"Since drush make is automatically mapped to Drush 6, you may need to cleanup your environment before running the build with two commands: drush cache-clear drush and rm -f -r ~/.tmp/cache."
or if this is just normal.
We should really write a book with all these tuts.
Makefile for install profile
I had no problem creating a platform with the makefile generated by drush.
It is quite simple: after navigating to an existing Drupal installation, the command will generate an example makefile which will be placed in the platform.
By customizing that makefile you can create another platform, all good.
But, what happens when you want to create a platform for an install profile?
Themes from themebrain.com, for example, have a starter kit that includes core, some necessary modules, and the theme itself all ready to go.
I am thinking of opening up that starter kit locally and customizing the makefile accordingly, anybody have a better idea?
Can the makefile be generated locally?
Answering my own question
Can the makefile be generated locally?
Answer is yes!
But not easily.
1) I had to install the install profile in my local server (apache2)
2) then navigate to install directory: /var/www/html/my_install_profile
3) drush make-generate my_install_profile.make
Lots of warnings in my make file and stuff to fill in manually, also the install profile has warnings about deprecated functions, but all this is unrelated to the procedure above.
How to generate makefile from current site
I am trying to use "drush generate-makefile" from one of my sites, which is on Commerce kickstart Platform.
Everytime I run:
"drush @my-site generate-makefile myfile.make ~/static/my-folder -d"
it goes on for a minute or so, then stops at the end with unrecoverable fatal error:
Error: Call to undefined function drush_make_error() in
/opt/tools/drush/7/drush/commands/make/generate.contents.make.inc