4 ms·
Since it isn't clear from the article: Is this "git deployment" just for the code components of WordPress (e.g, core upgrades, themes, and plugins), or does it
by duskwuff 14y ago
Since it isn't clear from the article: Is this "git deployment" just for the code components of WordPress (e.g, core upgrades, themes, and plugins), or does it cover content in the database as well? The latter would be much more interesting and useful.
- loeschg 14y agoThat would be some tricky git work. I'm fairly sure some sort of separate database configuration would still be needed (such as modifying the wp-config file). Jump down to step 7 here (http://wp.tutsplus.com/tutorials/hosting/wordpress-development-and-deployment-with-mamp-git-and-dropbox http://wp.tutsplus.com/tutorials/hosting/wordpress-developme...).
- austingunter 14y agoWe're recommending that core not be part of the deployment, since that could conflict with normal versioning of WordPress. It covers files and database. Check git.wpengine.com for the super in-depth coverage.
- aaronjorbin 14y agoIf you want to keep your content in version control, checkout this project - https://github.com/scottgonzalez/grunt-wordpress https://github.com/scottgonzalez/grunt-wordpress .
- pangram 14y agoYeah, I keep my blog posts in text files via git, and just push up to my server using XMLRPC. https://github.com/brool/wordpress-shuffle https://github.com/brool/wordpress-shuffle