About this plugin
json synchronised with the plugins installed.
Usage
Once installed the plugin should be largely set and forget, however there a couple of gotchas.
org plugins repository will still be added you will need to manually modify the repository (eg. wpackagist, wp-premium or using a custom installer or repository) or add your custom plugins first. WP Composer Sync will then honor these repositories and keep them synchronised as well.
2) When composer installs a package, it completely empties the target directory before installing the new files. g. php) will be wiped away on install or update.
php file in the parent directory of the WordPress path (WordPress can find it there automatically) and replace the wp-content directory with a symlink to your real wp-content folder. See link for more details.
3) Compposer require versioning wildcards (eg. *, etc) will not be honoured (as WordPress does not adhere to this). They will be replaced by the exact version number in use by WordPress.
About
Why?
Composer is a great way to manage WordPress and its plugins. However in real life it runs the risk of becoming outdated with the actual contents of the website when admin users are installing plugins via wp-admin or S/FTP.
How?
json file for any outdated or unfound plugins and will automatically add them to the require section.
Roadmap
The plugin is production ready however there are some additional functions and features which will be added in the future:
com/balbuf/composer-wp and wpackagist
2) Currently only syncs plugin and wordpress core, add ability to sync themes
3) Research some ways to monitor plugin-uploads and changes more effectively (eg. link link, link and link or Transients link link or link )