<br><br><div class="gmail_quote">On Fri, Mar 6, 2009 at 6:08 PM, Troy Arnold <span dir="ltr"><<a href="mailto:troy@zenux.net">troy@zenux.net</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;">
<div class="im">On Fri, Mar 06, 2009 at 11:30:24PM +0100, George wrote:<br>
> I'm testing the idea of having a local repos of drupal and the essential<br>
> module (and some not so essential modules) and checking out when i start<br>
> a new drupal project, and installing. of course this has the negative<br>
> that modules and drupal slowly fall out of date, but i find it<br>
> incredibly quick just to checkout, and start with the all the modules,<br>
> and take away what i don't want.<br>
<br>
</div>It sounds to me like a pretty terrible idea to start with something that is<br>
already out of date. If you want a rapid start, why not just run multiple<br>
sites out of one Drupal install?<br>
<br>
Also the drush module is pretty darn spiffy for quick module installs.</blockquote><div><br>Do you have an example of this? <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<div class="im"><br>
> i'm thinking about combining this with an install profile to<br>
> automatiically enable the core essential modules cck / views etc to<br>
> remove an extra layer of module enabling!<br>
<br>
> do any of you do anything similar? or do you have a different system?<br>
<br>
</div>I have a Drupal project that periodically needs to get cloned into a new<br>
instance. I ended up writing a Perl script to handle the tedious parts of<br>
cloning the database, copying over and resources, erasing the un-needed<br>
content and writing a new settings.php. That's probably a raunchy hack,<br>
but it was easier (for me) than learning the install profile system. It<br>
does require that you understand Drupal's database schema very well. </blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
It's a slightly different question than what you're asking, but for<br>
maintaining Drupal sites with a minimum of hassle I use a method largely<br>
based on David Grant's writeup:<br>
<<a href="http://www.davidgrant.ca/maintaining_vendor_sources_with_subversion" target="_blank">http://www.davidgrant.ca/maintaining_vendor_sources_with_subversion</a>><br>
<font color="#888888"></font></blockquote><div><br><br>I pretty much do the same thing, but end up doing a bunch of configuration by hand. I too was hoping to learn the install profile to create a baseline of modules I want all the time.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><font color="#888888"><br>
-t<br>
</font><div><div></div><div class="h5"><br>
_______________________________________________<br>
consulting mailing list<br>
<a href="mailto:consulting@drupal.org">consulting@drupal.org</a><br>
<a href="http://lists.drupal.org/mailman/listinfo/consulting" target="_blank">http://lists.drupal.org/mailman/listinfo/consulting</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Christian<br>