Git Management for WordPress

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.

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.<p>Storing the DB state in GIT is going to be an issue with a site of any substance.

I&#x27;ve done this before (though not using this solution), and I&#x27;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&#x27;t worth it. Perhaps only monitoring a couple directories (such as plugins) would be better, but too limited for a serious whole-framework solution.

Slightly offtopic: was surprised yesterday when publishing my first plugin at wordpress.org to find they use SVN.<p>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&#x27;s SVN repo. :)<p>[1] <a href="https://github.com/pdclark/deploy-plugin-to-wordpress-dot-org" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;pdclark&#x2F;deploy-plugin-to-wordpress-dot-or...</a>

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&#x27;s amazing and scary.

Great job: making Git work outside it&#x27;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&#x27;t let the naysayers get you down!

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

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

Trying to compete with versionpress.net?