I'm just wondering, would you be friendly to doing the same with the '/profiles' directory that it currently does with the '/sites' directory? The way I see it, profiles are projects in their own right, so if making a complete system, why not include those as well (also a theme and modules can be bundled in a profile to restrict use of those projects to sites that were installed using that profile, so in the site upgrade from one version to the next, you'll have to copy the specific profiles manually as it is).

Currently, I'm only addressing the create command, though it would have to be taken into account when making a new multisite (ie drupalupdate) in general (haven't observed that in action yet).

I only ran the create a few moments ago, but I see this is missing.

Comments

fl3a’s picture

fl3a commented
Component: Miscellaneous » Code
Assigned: Unassigned » fl3a
Status: Active » Closed (fixed)

Thanks for pointing me on this needful one.

The 'create' command now handles profiles in the same way like it does for sites,
i also updated the structure / schema on the project pages.

Changes to the 'drupalupdate' are not necessary
because it automaticly detects any included symlink and renames the target if it already exists.

If you try out 'drupalupdate', i am looking forward your feedback!

fl3a’s picture

fl3a commented
Status: Closed (fixed) » Fixed

Status: Fixed » Closed (fixed)

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