<div class="gmail_quote">On Wed, Jul 15, 2009 at 5:54 PM, Bevan Rudge <span dir="ltr"><<a href="mailto:bevan@civicactions.com">bevan@civicactions.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
At CivicActions we have a tool (pushdb --xFix) that fixes the paths in<br>
the files directory and elsewhere in the db, which we run when copying<br>
an instance of the site to a staging environment. However this<br>
approach is becoming unsustainable and we are considering using a<br>
separate instances of Drupal core in each and every staging<br>
environment so that they all use sites/default.<br>
<br>
What this means is that much of the time this featurebug is such a<br>
PITA that Drupal's multisite features don't work for staging<br>
environments. In my own sandbox I don't use multisite for staging<br>
environments at all, because of this issue, Do others?<br>
</blockquote></div><br>I don't use multisite for managing dev, staging and production environments. In my workflow, it would be *more* complicated to use this method. I put the entirety of Drupal core into version control and deploy working spaces straight from version control. This makes it much easier to control exactly what and when code is pushed to production, and enable the ability navigate through the history to find sources of bugs.<br>
<br>The only time I use multisite is for actual separate, yet integrated websites. The most common use for me are multiple websites that share tables, like the user-related tables.<br>