Git Management for WordPress

http://revisr.io

by matthijs_ • 12 years ago

70 26 12 years ago

revisr.io

metric• 12 years ago

So what would you say is the benefit of this over a basic github integration?

rebelidealist• 12 years ago

database changes I think?

brokentone• 12 years ago

It seems as though it works in reverse from a normal git setup--items which get changed on the server directly through say a UI initiated upgrade can be tracked and reverted in GIT from a dashboard. Kinda cool for single server installs.

Storing the DB state in GIT is going to be an issue with a site of any substance.

aikah• 12 years ago

Wordpress in next to not manageable with git anyway in my experience.The plugin system is totally broken when it comes to versioncontrol. Anything added to wordpress might f.. up the db or the cms itself. Wordpress codebase is f.ed up, ugly, badly architectured yet this is the most popular CMS and its ecosystem is huge. It's amazing and scary.

woah• 12 years ago

You sound like you may not know how to do it. I manage a medium-large sized site with Wordpress and git and it works great. Why would you ever try to check plugins into git? You are not supposed to touch anything outside of your theme folder. I have never had any issue updating anything.

morgante• 12 years ago

You are not supposed to touch anything outside of your theme folder.

Uh, what? Any medium/large site inevitably ends up with a few custom plugins.

paultannenbaum• 12 years ago

Wordpress is less than ideal for managing via git, primarily due to their plugin architecture. The best way I have managed to use git is to put the repo at the wp-content level and only watch the theme and plugin directories. Then anytime I make updates to a plugin or group of plugins, I make sure to commit those changes as a seperate commit to what I am normally working on. It is tedious and hacky, but it at least gets me basic version control functionality with the ability to roll back on any code that can effect theme functionality.

rwhitman3• 12 years ago

This is my workflow as well. Not ideal, but better than nothing.

Though I will say the biggest pain point with Wordpress is syncing and merging DB changes amongst team members, since so much of WP configuration is stored in the DB this becomes a real point of frustration especially on very large sites. I'd peg that problem as a much higher priority in terms of WP workflow than how to manage git inside WP admin.

nader• 12 years ago

this is a massive problem with all kinds of CMS including Drupal which we are using often. Drupal 8 is introducing configuration management, i.e. saving database configuration in yaml files which makes them "gittable". I hope wordpress and other CMS will also adopt this or a similar way.

twodayslate• 12 years ago

Trying to compete with versionpress.net?

Already__Taken• 12 years ago

Considering this is shipping I'd say it's rather the other way around.

Versionpress sound like they're going to try something a bit smarter with the database file though.

saddestcatever• 12 years ago

Version press still doesn't have a defined pricing structure. Competing against Open Source on Github doesn't bode well for them!

USNetizen• 12 years ago

I've done this before (though not using this solution), and I'll never do it again. Managing Wordpress (and the database backups) with Git causes ENORMOUS history files over time, to the tune of many gigs on the server depending on the size and configuration of the site. It isn't worth it. Perhaps only monitoring a couple directories (such as plugins) would be better, but too limited for a serious whole-framework solution.

koberstein2• 12 years ago

I use a .gitignore in root directory and ignore everything but the files that I control - theme and custom plugins.

pea• 12 years ago

Great job: making Git work outside it's familiar environment is a headache, but such an important problem to solve. It looks like they are some point on the way to doing it with Wordpress, so all the props to them. Keep on keeping on and don't let the naysayers get you down!

hippich• 12 years ago

Slightly offtopic: was surprised yesterday when publishing my first plugin at wordpress.org to find they use SVN.

Thankfully there was a deploy.sh script on github [1] which could be used to deploy your plugin from git repo straight to wordpress.org's SVN repo. :)

[1] https://github.com/pdclark/deploy-plugin-to-wordpress-dot-or...

koberstein2• 12 years ago

Very useful for situations where SSH access is not allowed but exec('git'); is :)

Git Management for WordPress

Related Stories