site relationships

What do you think of

+-----+-----+--------+
| nid | rid |  type  |
+-----+-----+--------+
|  42 |  3  |  clone |
+-----+-----+--------+

Where nid = the site, rid = the nid of the 'parent' or 'related' site, and 'type' being what made the relationship (which would simply be the $task type.

Then we could do various sorts of mapping in Hosting so that it would display sensible information in the hook_view(), similar to how we map the site status from integers to proper wordings in hosting_site

You'd then be able to query this table via the appropriate API hook to determine whether to override the 'site already exists' restrictions.

Perhaps also a configurable setting in Clone along the lines of 'Allow cloned sites to be overwritten?' or something would be nice too.

Edit: sorry some of the above should've been posted to #699922: multiple clone support.

http://drupal.org/project/noderelationships

We'd need to add CCK (and nodereference) and Views as dependencies, we have modalframe and jquery_ui already

Maybe nodereference would be enough already but not sure if we want to drag CCK into Aegir

Initial dev branch has been pushed to g.a.o.

This is early days and entirely frontend. Features:

1) Tried to add as many API functions as I could think of that might be useful for future abstraction
2) Clone implements one of these functions to add a relationship between two sites in the drush post_ task
3) Site nodes have a MENU_LOCAL_TASK called 'Relationships' consisting of a table showing all existing relationships, making a distinction between where a site holds a 'parent' or 'child' relationship of the other. (i.e if Site B is a clone of Site A, Site A is thus the parent in the relationship). Screenshot attached

I added a _settings hook to Clone that simply provides a way to turn 'Overwrite' on or off, based on whether one should be able to overwrite a previous clone of the same name. But no logic to actually handle this exists in the backend yet. The clone form's hook_validate will need to check for this setting before complaining of a URL that already exists, and the backend will need to perform a provision-delete on a site before being able to restore from a tarball if the platform is the same target as the previous edition of the clone's.