We currently look for a platform.make file in the site git repo.

But if we have a stable platform, why not re-use it for multiple sites. I guess we could make it part of the create project wizard...

I'm undecided about this. Having a separate platform copy might be better for xdebug, but would take away the advantage of mass migrating sites to a new platform version.

Related: #1915854: Support building environments from makefiles or install profile repos.

Comments

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
commented

Just to be clear here, we're talking about dev/testing environments, right? Not staging/prod? The purpose of #1915854: Support building environments from makefiles or install profile repos., along with the 'update' task in hosting_tasks_extra is to enable 'normal' Aegir updates (via migrations) for production sites.

In dev/testing environments, I kinda like DevShop's site+platform=environment approach. In my experience at Koumbit, mass-migrating dev sites to new platforms caused more problems than it sought to solve. In fact, I believe we've abandoned that practice, and just build new platforms and allow devs to migrate themselves. I could be wrong though...

Perhaps we could elaborate a clear use-case/workflow, and see whether this or another solution is preferable. For example, perhaps we need a 'rebuild' or similar task for sites in dev, which we could then schedule for a whole platform via VBO.

helmo’s picture

helmo commented
Issue summary: View changes
Status: Active » Closed (won't fix)