you all know me by now, i always have issues....
so i am reading docs so i can understand things better and i come across this page
http://omega8.cc/the-best-recipes-for-disaster-139
in part this paragraph:
[blockqoute]How to get all kinds of failed migrate or clone tasks? Very easy. Simply use sites/domain-name/modules space for your code. This will guarantee many half-broken migrations with duplicates of the same site existing in two platforms, with fatal errors because some required include file in some module no longer exists, or not yet exists, as all paths to sites/domain-name/modules change on the fly when domain-name changes, so some entries in your site’s system table will cause either failed and reverted tasks in Aegir or some nice WSOD, until you will repair registry. No, really, don’t use sites/domain-name/modules for anything and save yourself headaches and frustration.
[blockqoute]
does this mean i shouldn't cherry pick modules under specific sites where i need them? i should put any modules i want on a site under sites/all? is it okay to just enable specific modules, theme on what sites i need?
i have 30 sites and counting on octopus, the sites all do different things.
Comments
This is what I think from
This is what I think from what I've learned so far. If that's not true, then forgive my ignorance:
It seems the only thing to do in order to follow the Aegir concept is to put all modules under sites/all/modules.
The alternative is putting modules in a profile - but this can happen only with newly created sites so you can't go down that road with existing sites.
I'm on the same boat, hundreds on modules under sites/all/modules makes it hard to remember what module is used by each site.
Another alternative is to create a platform for each site but the upgrade process is very time consuming and in my case, out of question.
Aegir is great when you start from scratch, but migrating existing sites to Aegir comes with a price.
Another alternative is to
You should create a platform for each different type of site, don't use one big platform for everything. The benefits of separate platforms is that you can control them separately of each other, upgrade them without having to upgrade all of them.
Upgrading is as easy as cloning the platform, cloning the site to the new platform to make sure everything works, and if so migrating the site to the new platform.
omega8 do have a tutorial on
omega8 do have a tutorial on moving sites across different profiles in Aegir http://omega8.cc/migrate-sites-between-install-profiles-easily-111 so you can "go down that road" with existing sites.
creating a new platform for each site is not so bad if you manage each site with a makefile. If you are finding it difficult to remember what modules are used by each site it sounds like you could really benefit from incorporating makefiles into your workflow anyway.
a lot of the work can be done automatically for you by drush if you use their make-generate feature.
imo, putting unrelated sites on the same platform just for "convenience" sounds like a false economy to me as you'll potentially run into problems and hard-to-debug unexpected behaviour as soon as you start patching shared modules.
thanks to everyone for the feedback
"creating a new platform for each site..."
What?
users should create their own platforms? i thought that is what was octopus for?
i thought these profiles/distributions/platforms took months, sometimes years to create.
are you using the word "platform" in a different way?
i was hoping to avoid building sites offline and uploading them. i thought it would be easier to use a profile in octopus and add any extra modules needed. everything seems to revolve around a few drush commands
are they any video tutorials on makefile? the documents dont make much sense
=======
=======