1. 1. How Free Trials Work
    1. 1.1 Free Trial Guidelines and Regulations
  2. 2. Installing the WPMU DEV Dashboard Plugin
    1. 2.1 Installation Instructions
  3. 3. Installing WPMU DEV Plugins & Themes
    1. 3.1 Install WPMU DEV Plugins
    2. 3.2 Download WPMU DEV Themes
    3. 3.3 Download Previous Versions of WPMU DEV Plugins and Themes
    4. 3.4 Retired Plugins
  4. 4. Getting Support
    1. 4.1 The Good Support Ticket
    2. 4.2 Initial Troubleshooting
    3. 4.3 Opening a Support Ticket
    4. 4.4 Enabling Support Access
    5. 4.5 Using the Contact Form
    6. 4.6 Using Live Chat
    7. 4.7 Finding a Pro
    8. 4.8 Additional Support & Community Tips
  5. 5. WPMU DEV Translations
    1. 5.1 The Interface
    2. 5.2 Importing Translations
    3. 5.3 Exporting Translations
    4. 5.4 Using Translations
    5. 5.5 Configuring WordPress for your Language
    6. 5.6 Reward and be Rewarded
  6. 6. Installing WPMU DEV Plugins via Composer
    1. 6.1 Composer Integration Examples
Docs / / Installing WPMU DEV Plugins via Composer

6. Installing WPMU DEV Plugins via Composer

Written by Michelle Shull | Last updated: February 14, 2017

If you are the advanced developer type and like to manage your WP site via the Composer package manager WPMU DEV has full support for that! We are now publishing our own Composer repository.

You can also check out our blog post on using Composer with our plugins here.

6.1 Composer Integration Examples

Link to chapter 1

All packages are protected by basic auth with your API key as the username, you can leave password blank. All you have to do is add https://premium.wpmudev.org/ as a composer repository to your WP root Composer.json file. Here is an example of what you would need to add to your Composer.json file to install the latest version of Spirit theme and MarketPress plugin:

Package names use the url slug of the project as found in our listings https://premium.wpmudev.org/projects/category/plugins/, not necessarily the folder name.

Here is a little example of calling “composer update” after adding our repo and some packages.

composer-test

After entering your API key once, Composer will prompt you to save it in a private location, which is fine. Please note that it’s highly recommended not to save your API Key into Composer.json, as that is often published and publicly accessible which is a violation of our TOS. So if you save it make sure it’s in the proper auth.json file which is excluded from public repos.

The WPMU DEV repo also has some basic dependency management, for example adding wpmudev/luke-sara theme will automatically install the required wpmudev/upfront parent theme, or a BuddyPress plugin will require buddypress/buddypress package from packagist.