Composerpress

Composerpress Retroactively attempts to create a composer.json for a WordPress site. On activation, a composer.json menu appears in the admin area under the Tools menu. This page shows what composerpress thinks a composer.json that will generate a website close or identical to the site the plugin is installed on might look like. Includes support for detecting/reverse engineering composer packages via: - packagist - wpackagist - private mercurial repositories - private git repositories - private svn repositories - non-composer plugins residing in git/svn/mercurial repositories Installation Notes Install as a regular plugin and then run composer install on the wp-content/plugins/composerpress plugin folder to install dependencies. For instructions on installing composer: see here for nix and here for Windows TODOs: Currently ComposerPress does not perform any checking with wpackagist #2 (or similaries), leaving open these problems: - when a TextDomain doesn't match a Plugins Name ? - when a plugin doesn't match its Folder Name ? - when a Plugin is Custom to a site (ie doesn't exist in the wp.org repo)? Keep in mind 1. At present, if composerpress can not find the so