Posted by ckosloff on March 6, 2014 at 2:07am
I am confused here because of conflicting instructions.
I have read Bill Powell's article on About.com and he recommends adding modules in /sites/all/modules, not on site/mysite/modules, and offers an explanation for that.
The email I got from BOA recommends to add modules to the platform, which seems more in line with BOA workflow.
There are still other recommendations, in the readme.txt for Drupal, that do mention the sites/mysite/modules approach, but that does not apply to Aegir.
So, where to load modules and themes?
Comments
https://omega8.cc/the-best-re
https://omega8.cc/the-best-recipes-for-disaster-139 and check #4.
Thanks for answer. Yes, I had
Thanks for answer.
Yes, I had read that before but did not understand fully the implications, what is not clear in that document is the "install profiles", it encourages you to learn that but does not show where.
I also suggest you download
I also suggest you download and read http://wiki.internetmachines.co.uk/mediawiki/index.php?title=BOA . It was enlightening for me being a noob as well.
Even though it is outdated, it will suffice to get a better understanding of the BOA ecosystem .
Thank you very much,
Thank you very much, downloaded.
Now give me some time to digest this large chunk.
sites/all/modules is within a
sites/all/modules is within a platform. This just means that you should add modules to the correct platform, i.e. the folder containing drupal core. In other words, pick the correct platform from the list of drupal-7.24.1-dev, drupal-7.24.1-prod, pressflow-6.29.1-dev etc. when you want to add a module to one of them.
The location inside the platform could be sites/all/modules, or maybe sites/all/modules/contrib if you also want to use sites/all/modules/custom for your own modules. And modules may also live in an installation profile in your own custom platform.
(Base) themes go in sites/all/themes, though you may want to put site-specific (sub)themes in sites/example.com/themes so they don't show up in other sites.
Omega8.cc are pointing to the about.com article so you can follow that. https://omega8.cc/how-to-organize-your-modules-into-a-platform-245.
Thanks again, ar-jan for your
Thanks again, ar-jan for your kind help.
I had read the article in about.com.
Looking at my install in sftp I see in the platform that contains some of my sites an "all" folder, with subfolders "modules " and "themes".
I suppose that is where modules and themes go, and not in the folders by the same name in the sites themselves.
Please note that the source of my confusion is that there is no /sites/all folder in platform it is simply /all.
Regarding install profiles I still have to learn that, will try to read related posts in Aegir handbook before posting anything here.
Makefiles is something I still have to understand but please don't reply here, in order not to start a humungous discussion, I will post separately on that subject, if needs be.
Hello ckosloff, Put any
Hello ckosloff,
Put any modules that may be shared with different sites in
'sites/all/modules' but any modules that are custom or rare, or specific
for a site in 'sites/specialsite.com/modules' this makes the site
more easily transportable, if it is a module like 'views' put it in sites/all
with drupal multisite (and boa) you can share code between sites
hth
Cheers
Make files
Just a comment on this if you are using make files to produce your platforms.
If you place the modules in the sites/domain.com folder, then when you create a new platform, those modules will not be updated and you will need to update them manually.
An alternative is to place 'custom' built modules - that you are writing in the site/domain.com folder
place all community based modules in the sites/all folder
create a separate platform for each distinct set of community modules. I have just one called 'mydrupal' that has all my generic modules in it.
This way, you can use the BOA Migrate feature to move to a new platform with all the new modules and it has a safe roll back if it fails. If you have many domains on a platform, those that file will still be in the old platform after migration and you can view the error and fix.
I like to keep the number of platforms down and use only half a dozen. One generic one with many modules. Others situation specific.
Another option is to use the 'profiles' as a mechanism to store community modules.
make files are your friend
Thanks for elaborate
Thanks for elaborate answer.
Makefiles is a subject that I still have to learn and practice.
I will be back on that after studying more.
Thanks for answer. Yes, I
Thanks for answer.
Yes, I already understood that.
I will be using Aegir to share code between sites, I like the workflow better than multisite, still have to understand all the intricacies.
Thanks for answer, reload. I
Thanks for answer, reload.
I already answered but for some obscure reason, my comment went to the end of the page.
Anyway, everything clear now regarding this issue.