[wp-hackers] Git best practices

Roger Chen (RogerHub) developer at rogerhub.com
Tue May 6 01:30:54 UTC 2014

Our developers use Vagrant with a simple configuration that sets up WPMU on
a VM with some essential themes, plugins, settings (from a database dump)
etc. Everything is kept under version control with git. Then, most of our
devs use rsync or something similar to test code on their VM. When they're
done, they commit back to git from their hosts (not within the VM). I find
it easier than hosting VM's centrally. If they're working on more than one
project, you can always setup multiple VMs. Unless there's some bizarre
reason why database data needs to be shared among developers, it's usually
enough to just check in updated code to version control.

I would highly recommend Vagrant, no matter what plan you go with..



On Thu, May 1, 2014 at 3:15 PM, Dino Termini <dino at duechiacchiere.it> wrote:

> Hi list,
> This is a question for those of you who have teams of developers working
> on multiple WordPress projects. What best practices do you follow to setup
> your dev environment with git? Does each developer get his own WP MU where
> he develops his piece of the project? (And how are those pieces reconciled
> with the git workflow?) Or they have a standalone wp install for each
> project?
> Thank you,
> Dino
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers

More information about the wp-hackers mailing list