cvs best practice

Events happening in the community are now at Drupal community events on www.drupal.org.
Anonymous's picture

I was needing some advise regarding CVS and file locations. I use 50-75 contributed modules on various sites.

What I'm curious about is how to best manage contributed products, e.g. modules, themes, installation profiles, languages, theme-engines, etc. (that may be about it).

I'm tempted to put the entire contributions repository in root/sites/all

[cvs -z6 -d:pserver:anonymous:anonymous@cvs.drupal.org:/cvs/drupal-contrib checkout contributions]

which would give me root/sites/all/contributions/modules, root/sites/all/contributions/themes, root/sites/all/contributions/theme-engines, etc.

This would make life easy when updating, but a pain when it comes to selecting a module (scrolling, and scrolling, and scrolling, to activate a module on a new site)!

Is there a way other than individual CVS checkout and update per module?

Comments

I use sites/all, most of the

sime's picture

I use sites/all, most of the modules are checked out by script, and I'm using an install profile to automatically install the primary modules so that I spend less time on the modules page.

So my modules in sites/all are 1. modules I use all the time and 2. modules that are abstracted (actions, panels).

By default, I don't download contrib modules that I use less than 1/3 of the time - I wait for the customer to ask. I will then (usually) put fringe modules in the sites/example.com directory.

Couple of questions/comments ...

daouverson2's picture

Thx for taking the time.

I get the installation profiles, and am getting ready to automate that; the modules have to be in sites/all though, right?

What are you doing in regards to "checked out by script"? Right now, I'm checking out via CVS.

========
Doug Ouverson

For the profile, your

sime's picture

For the profile, your modules can be in any of the normal locations.

The script I'm using just automates the manual labour prior to the install profile.
http://cvs.drupal.org/viewvc.py/drupal/contributions/profiles/emspace/em...

(The profile I just linked to is a work in progress, it's not usable yet)

For extra funkiness...

niklp's picture

... check out the "drush" module - this can install stuff for you from the command line very quickly, and also perform updates and do cool sql things too. If you're doing multisite this might come in handy in a number of ways.

Kineta Systems - Web Development in Nottingham, UK

NO DRUPLA-5 BRANCH

daouverson2's picture

Noticed there was no DRUPAL-5 branch, and all 5 tags are in beta. Any idea on when drush will have a solid non-beta 5 branch?

========
Doug Ouverson

I wouldn't worry about that

niklp's picture

I wouldn't worry about that too much, it's one of those constantly in dev projects really, I think. All the stuff I've used it with has worked just fine, using the .dev version (IIRC). You'll note too that Devel is still in dev after over 4 years...! ;)

Kineta Systems - Web Development in Nottingham, UK

Multisite

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: