What we do with distributed development is to make an svs:ignore on the settings file, while putting a mysqldump synched with revisions. With scripts, so that one does a checkout, runs a script and is all set to go on the local installation.
<br><br>What you are saying would certainly be more elegant, so if you make progress, please comment!<br><br>saludos,<br><br>Victor Kane<br><a href="http://awebfactory.com.ar">http://awebfactory.com.ar</a><br><br><div><span class="gmail_quote">
On 8/16/07, <b class="gmail_sendername">J-P Stacey</b> <<a href="mailto:jp.stacey@torchbox.com">jp.stacey@torchbox.com</a>> wrote:</span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
One of the big problems we have is that many developers working on a given<br>codebase: this means the codebase is in subversion and people check it out<br>to their own machines, work on it, check changes back in.<br><br>
Some developers develop on the same machine, because their desktops are<br>WinXX and setting up LAMP stacks takes time. On this machine, whilst they<br>can check out site-specific codebases to e.g.<br>sites/developername-
<a href="http://clientname-devel.example.com">clientname-devel.example.com</a> and hence develop in their<br>own sandboxes, it's difficult to keep the site under revision and yet not<br>have people be forced to share a database by
settings.php .<br><br>But with the above a high-priority module could switch quickly and cleanly<br>between developers' own sandboxed databases: does that sound right? How<br>would you sneak in before any of the other modules? Would the following at
<br>the end of settings.php be sufficient:<br><br> db_set_active($_SERVER['HTTP_HOST']); // defaults to 'default'<br><br>Or is that too hacky? Can you even call a function from within settings.php<br>
(notwithstanding the argument of "would you want to?")<br><br>Somewhere among all this is functionality to make Drupal a good deal more<br>"enterprise", for whatever that hackneyed term is worth. Transparently
<br>distributed development for large-scale, independent CMS teams on their<br>clients' behalf.<br><br>Cheers,<br>J-P<br>--<br>J-P Stacey<br>+44 (0)1608 811870<br><a href="http://torchbox.com">http://torchbox.com</a><br>
</blockquote></div><br>