So what is the best process for setting up a large community site using WordPress with git version control? Multiple people submitting changes etc, testing area and easy way to update the live site. How would you do it?
Leave a Reply
You must be logged in to post a comment.
The most prudent way is to use a staging server.
The workflow would be:
Some Notes:
Have only one/two people actually manage the master push to the staging server, this allows them to review changes and have a certain amount of control over what goes on, also it is way less confusing.
This is strictly for code changes, content based changes are way more complex and would need several other “layers” to ensure database compatibility/sync.
Sending from staging to live is a topic in of itself, you can use automated tools, ftp, even DVCS itself, it really depends on your environment.
An alternative is to use a PHP based PAAS servive ( there are now several), they can automate much of this process, I recently reviewed them all and each one has a different feature set and quirks ( most of these services are really new).
For example here is a really boring video I made on syncing a live site through github ( using Engine Yard), the downside is that this service has no actual file server and in the long run made it very difficult to work with, but some PAAS services do support this.(I think they are adding it soon as well)
http://www.youtube.com/watch?v=8ZEiFi4thDI
If i don’t misunderstand, you have a team. Your teammates changing your WordPress’ codes. For example; developing plugins, themes, changing WP core files etc.
So you can add your WP directory to
git
directly.If
git
installed to your server, go to your WP root directory via ssh connection. And then, executeThis will initialize a git repo to this dir. And then add all files
And then send your first commit :
Now your teammates can get repo with
NOw everyone can modify your WordPress and commit their changes to server.