Posted by leevh on January 8, 2012 at 7:43am
Hi all, I was wondering if anyone knows the best way to base a custom makefile off of, for instance, a BOA pressflow platform? Since Omega has spiced up these platforms with extra useful modules etc, I would want to have my custom platform always pull from the latest BOA pressflow BEFORE adding any of my custom stuff. Anyone done this? thanks!
Comments
It works out of the box already
You shouldn't add the modules that are added by BOA to your Octopus platforms (also your custom platform), automatically (every morning). Please read: http://omega8.cc/extra-modules-available-in-all-platforms-123
[EDIT] Note that you can add the magic symlink to your new custom platforms on demand by running the script which normally runs only once, every morning:
bash /var/xdrago/usage.shThank you
Well that just makes things too easy! ;) Thanks for the response Omega, its much appreciated.
Cloning platforms
My first comment here so before anything else I'd like to thank omega8cc for her amazing work!
I've been trying to add a new platform based on the default pressflow-6.24.1-dev because when I attempt to create a Pressflow platform from a makefile , I get a drupal 6.22 version of Pressflow!
So far, I've tried to add platforms using two methods.
1/ Using a makefile
2/ Copying a Drupal folder
Both methods work well, except when I try to copy/clone one of the default platforms!
The platform gets installed but I can't verify it. Here's the error:
Invalid or empty make file: /data/disk/dev/static/platforms/pressflow-6.24.1-customCommand dispatch complete
Peak memory usage was 5.92 MB
Could not download platform using drush make. No platform present
That would seem to indicate that I have to use a makefile, but according to step 3 in the following page, I know I should be able to add the path to the folder
http://omega8.cc/import-your-sites-to-aegir-in-8-easy-steps-109
Actually, I find the following quite confusing:
The absolute path on the filesystem or public URL of a makefile that will be used to create the platform in the directory specified above. If the directory already exists, this file will be ignored.It gives me the impression a platform can only be added using the makefile method. Especially since the form label is "Makefile".
Another attempt was to use
drush make-generatefrom the pressflow-6.24.1-dev folder... but this fails too, as I get the error "The drush command 'make-generate' could not be found. ....".
Some makefiles are available here
http://drupalcode.org/project/octopus.git/tree/e05648179bfbc968f10e0fb5f...
but there are no pressflow 6.24.
Finally, when I try to cleanup and delete the failed platform, the task fails with the following message:
The directory /data/disk/dev/static/pressflow-6.24-1.custom does not contain a valid Drupal installationSo, what am I missing?
Thanks!
Missed the Publish Path
Apologies for the long unnecessary post!
So I finally managed to create a platform by copying a default one, here are the mistakes that prevented me from getting the platform verified.
Omega, you've done such a good job of automating everything and still I missed the point by overlooking something so basic!
Thanks again & hopefully my mistakes will help others avoiding doing the above!
Well, in fact it is a serious
Well, in fact it is a serious UX issue and we have to fix this to avoid this (expected) confusion.
For reference, here is a detailed how-to for this step:
We need to improve/fix both the how-to and inline help if we already enabled this feature by default.
Do we really need automation
Do we really need automation at this level?
I'd be happy with a basic "Publish Path" field