I wrote a PHP class that allows a plugin developer to incorporate updates from GitHub within their plugin. Here’s a link for it -> https://github.com/jkudish/WordPress-GitHub-Plugin-Updater
From my perspective there are two issues with your plan – Git and “conventional” structure. So basically everything. 🙂 Git (and version control in general) is a poor tool for whole site stacks. Been there, done that, it hurt a lot. What you call an “unconventional” structure with content separated from core has been a … Read more
General Questions answered Nr.1. Would like to have my git environment on my own server internally, not using Github to handle repos. The first thing I’d do is to check out composer and how it works with WordPress, which is a project by Andrey “@Rarst” Savchenko. Nr.2. Automatic creation of subdomains upon git branch creation … Read more
Git for plugins: Use Composer for plugins which are already packaged on packagist or wpackagist. Add them to composer.json. Use TGM Plugin Activation for other plugins. Then, use Git to manage composer.json and the changes in the TGM plugin. The hardest part is to sync database: Definitely, we should share database. Reconfigure a plugin settings/options … Read more
I’m one of the developers of WP Migrate DB Pro, and would like to answer @Ennui’s question: “Do you know if the db url replace script it runs takes into account serialized strings?” Yes, it does handle serialized data. In fact, that is the primary reason I developed the free version of the plugin back … Read more
I am not sure how much you know about using version control, but I recently switched from SVN to Git and find that to be great! Though it depends in you live site’s server has Git installed (or will let you). I have a Git setup on the live server also, running off a branch … Read more
There are 3 options from easiest –> Use only one remote database that you all connect to with lots of backups. That way you just have to worry about files and not the db. Use the import and export functionality built into WordPress and throw it into your version control right into the wp root … Read more
I use git for this and find it works really well. A few suggestions: Add your uploads directory (wp-content/uploads) directory to your .gitignore file. Run a web server and database server on your development system so you can test changes locally before pushing them to production. Keep your database connection settings consistent beween dev and … Read more
I’ve used git as version control for the whole WP installation and individual themes/plugins. Under normal circumstances, I don’t see the point for the first option, unless you want to keep all the plugins and WP version in sync with the git repo. In that case, you should definitely gitingore the upload folder, otherwise uploading … Read more
A common cause is cloning using the default (HTTPS) instead of SSH. You can correct this by going to your repository, clicking “Clone or download”, then clicking the “Use SSH” button above the URL field and updating the URL of your origin remote like this: You can check if you have added the remote as … Read more