I am beginning to use Aegir to manage my Drupal sites. I am trying to develop a set of best practices for platform creation. My current best practice can be outlined as follows:

  • Create a make file for the platform to use with kplatforms.sh. Include in the make file whatever version of core and contrib modules that I believe will be appropriate.
  • Create a development site based on this platform.
  • Identify additional modules that I need for this platform.
  • Update the make file to add these additional modules.
  • Use kplatforms to build a new platform.
  • Migrate my development site to the new platform.
  • Rinse and repeat until the platform is what I need.

Put another way, best practice would discourage adding modules to an existing platform.

Am I missing any crucial steps or am I making any mistakes?

Comments

helmo’s picture

helmo commented
Status: Active » Fixed

That sounds like a safe practice.

kerolar’s picture

kerolar commented

I'm on the same learning curve (a few days behind), what is kplatforms.sh script? Thanks

helmo’s picture

helmo commented

See the https://drupal.org/project/kplatforms project page.

kerolar’s picture

kerolar commented

Thanks for the lead. As a matter of interest how did you discover kplatforms? I'm actively reading Aegir Handbook which doesn't seem to be well maintained and I'm piecing my learning process together with Evernote. I've got as far as Aegir Drush make and was just about the make a start with make:-)

kerolar’s picture

kerolar commented

I found the source in #4 Aegir Contributed Modules. As a newbie, one needs to be patient to stitch all the available (and very good) Aegir documentation and other resources together. I'm getting there:-)

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.