Conflict with Drupal core 'path' attribute. Fix + deletion and prefixes too

:-}

On creation, almost everything seems to work, but I get a "Page not found" and a ridiculous URL
http://{druplethost}/?q=/var/www/{druplethost}/sites/{newdruplet}.{druplethost}
(my substitutions, that's not the ridiculous part. The /var/www is the problem.

Looking at druplet_generate_site() it's clear that a node is being created that is setting $node->path to something totally different to what Drupal thinks 'path' means.
While there is a chance that this would have worked anyway. ... It doesn't. Possibly because of the leading /
Anyway. It's not right.

I propose the druplet site filepath as stored in the node be relabelled to $node->druplet_sitepath (or something) to clarify the modules namespace.
In fact, as a best-practice, the custom fields could all be more clearly labelled, or packed into a

$node->druplet['host'];
$node->druplet['subdomain'],
$node->druplet['domain'],
$node->druplet['path']
$node->druplet['db_name']
$node->druplet['db_user']
$node->druplet['db_password']

sort of array. Just to be tidy and avoid conflicts.
Best-practice, but not strictly neccessary.

... actually, looking at the code more, half those attributes are only temporary, so the impact is lots less than I thought.

What do you think?
For now, I'll be renaming the 'path' away anyway.

I'm doing a bit of hacking, so I won't have a clean patch. I'm also looking at ways of inserting more parameters from the creation form to pass them to the install profile - to customize the build still further.
EG, CCK fields added to the druplet content type become (global?) variables that my .profile can read and do still more self-customization. or the $node object itself is just passed in.
... that's another thread.