In my local development environment (MAMP) I do tend to use a lot of symlinks. I also have one giant SVN repo which contains common modules that I don't maintain (admin_menu, token, etc.) which can be symlinked in bulk. - Ken Winters Randy Fay wrote:
Hi Ken -
How do you build a dev site using your root-level contrib module projects? Do you just symlink together a site?
This is a classic Drupal problem, and it's not really even solved well by git, which has submodule support, but not sure it makes everything better.
-Randy
On Sun, Jun 6, 2010 at 12:12 PM, Ken Winters <kwinters@coalmarch.com <mailto:kwinters@coalmarch.com>> wrote:
I use a single workspace for all my Drupal work (and a few other for code using different coding standards).
Then I do one "project" per module per active branch. For example, if I need to implement a feature in D7 then backport to D6, I'll have one "project" per. Importing a project via CVS makes this easy. Also, I can keep most of the projects closed and cut down on memory footprint.
I've also got one "project" per site, containing just code that is unique to that site. Custom themes, etc.
Long ago I had one mega-project with many CVS repos, but that was not flexible and grew unwieldy.
- Ken Winters
Syscrusher wrote:
I need to be able to manage my modules for multiple Drupal core versions, and also for multiple modules, and I'm looking for advice from others as to the "best practices" for doing this. How did you partition your development environment as far as workspace, project, and folder levels, with regard to Drupal core and module versioning standards?
-- Randy Fay Drupal Module and Site Development randy@randyfay.com <mailto:randy@randyfay.com> +1 970.462.7450