Skip to content

clarify puli installation #91

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 26, 2016
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions discovery.rst
Original file line number Diff line number Diff line change
Expand Up @@ -40,14 +40,18 @@ In both cases you have to install the discovery package itself:

As mentioned above, discovery relies on Puli. In order to use discovery, you need to also set up Puli.
The easiest way is installing the composer-plugin which automatically configures all the composer packages to act as
Puli modules:
Puli modules. For applications, simply do:

.. code-block:: bash

$ composer require puli/composer-plugin

This is only necessary in an application. However, you might also want to install the composer-plugin as a development
dependency in reusable libraries as well (for example to use discovery in tests).
If you need the composer-plugin for testing in a reusable library, make it a development dependency instead:

.. code-block:: bash

$ composer require --dev puli/composer-plugin


Read more about setting up Puli in their `official documentation`_.

Expand Down