By monkfish4d on
Hello,
I understand there are big websites out there that use Drupal... Sony MyPlay, Mixmag, Amnesty, etc... And I'm going to assume that these sites were built by a Team of Drupal developers working on the project at the same time.
I'm working with another Drupal developer and my idea was that we both work on it together but so far he's only been working locally which is holding things back...
How is this managed if nearly all the setting for Drupal are stored in a DB?
Does anyone work on Drupal sites in teams?
Thanks in advance, N
Comments
in my opinon, drupal is not
in my opinon, drupal is not suitable team work.
---------------------------------------------------------------------------
Drupaluser.org---Sea water droplets together
The best way I've found is
The best way I've found is to have everyone working against a central development installation.
The other thing that could be done would be to use output from mysqldump to create a text file which could be used as a way to pass the database around for installation on various machines. Not ideal, certainly, but feasible if you're careful with versioning.
If others have better ideas, I'd certainly love to see them too.
We use a CI server
We use Continious Integration, so each developer, when they check things in, work together. A lot of times folks will sit down in the office, or at a cafe, and just hammer through features as a team, diving up the work. If you want to work on the same things at the same time, you're going to have trouble with any database driven framework.
Working off the same server is sometimes asking for trouble, as database changes can break the site for periods, which brings other developers to a screaming hault.
If you want to work more directly, consider pairing. That works really well for teaching people how to do Drupal.
My 2c. All the best.
--------------------------------------------------
WorkHabit, Inc.
We make business social.
http://www.workhabit.com/
Using a CVS
I am not sure what you are trying to address and I may have misunderstood what the issue is, but since nobody has mentioned it...
I would suggest that you setup your Drupal test and development installation on a server accesible by all. On the same server I would setup Subversion as a control versioning system I would make my Drupal directory the local directory and work that way. It still allows you to setup local test environment from the same Subversion server for first draft work, syncing the local db every so often, again from the maser test server. This would give you a great history of changes with line by line differences highlighted.
Of course you may be able to use other CVS. I just ahppen to like Subversion. In fact although I am working alone I use such a setup and commit very often, which easily allows me to undo the changes or simply examine them. In fact I use it even for content creation. I probably have 30 or more candidate posts at different states. Some are just outlines, some are more fleshed out or the finishing touches are being applied.
Hope this help,
Enjoy,
www.ZuNOB.com