info/php-the-right-way
1
0
Fork 0
mirror of https://github.com/codeguy/php-the-right-way.git synced 2025-08-16 10:43:58 +02:00
Code Issues Projects Releases Wiki Activity

Reword DM to use Composer as global PM

Browse Source
This commit is contained in:
Maxime Fabre
2014-10-21 19:57:26 +02:00
parent ed7fb77307
commit 779932b272
2 changed files with 10 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
_posts/04-01-01-Dependency-Management.md
View File

@@ -6,9 +6,4 @@ anchor: dependency_management
There are a ton of PHP libraries, frameworks, and components to choose from. Your project will likely use several of them — these are project dependencies. Until recently, PHP did not have a good way to manage these project dependencies. Even if you managed them manually, you still had to worry about autoloaders. No more. There are a ton of PHP libraries, frameworks, and components to choose from. Your project will likely use several of them — these are project dependencies. Until recently, PHP did not have a good way to manage these project dependencies. Even if you managed them manually, you still had to worry about autoloaders. No more.
Currently there are two major package management systems for PHP - Composer and PEAR. Which one is right for you? The answer is both. Currently there are two major package management systems for PHP - Composer and PEAR. The former is the main package manager to use for PHP, however for a long time PEAR used to fill that role, and you may still find references to it so it's a good idea to be aware of its extistence too.
* Use **Composer** when managing dependencies for a single project.
* Use **PEAR** when managing dependencies for PHP as a whole on your system.
In general, Composer packages will be available only in the projects that you explicitly specify whereas a PEAR package would be available to all of your PHP projects. While PEAR might sound like the easier approach at first glance, there are advantages to using a project-by-project approach to your dependencies.

11
_posts/04-02-01-Composer-and-Packagist.md
View File

@@ -40,7 +40,7 @@ The path `$HOME/local/bin` (or a directory of your choice) should be in your `$P
When you come across documentation that states to run Composer as `php composer.phar install`, you can substitute that with: When you come across documentation that states to run Composer as `php composer.phar install`, you can substitute that with:
composer install composer install
This section will assume you have installed composer globally. This section will assume you have installed composer globally.
### How to Define and Install Dependencies ### How to Define and Install Dependencies
@@ -70,7 +70,7 @@ This is most useful when you define your version requirements flexibly. For inst
### Update Notifications ### Update Notifications
To receive notifications about new version releases you can sign up for [VersionEye][3], a web service that can monitor To receive notifications about new version releases you can sign up for [VersionEye][3], a web service that can monitor
your GitHub and BitBucket accounts for `composer.json` files and send emails with new package releases. your GitHub and BitBucket accounts for `composer.json` files and send emails with new package releases.
### Checking your dependencies for security issues ### Checking your dependencies for security issues
@@ -86,3 +86,10 @@ The [Security Advisories Checker][4] is a web service and a command-line tool, b
[5]: http://getcomposer.org/doc/00-intro.md [5]: http://getcomposer.org/doc/00-intro.md
[6]: https://getcomposer.org/Composer-Setup.exe [6]: https://getcomposer.org/Composer-Setup.exe
### Handling global dependencies with Composer
Composer can also handle global dependencies and their binaries. Usage is straight-forward, all you need to do is prefix your command with `global`. If per example you wanted to install PHPUnit and have it available globally, you'd run the following command:
composer global require phpunit/phpunit
This will create a `~/.composer` folder where your global dependencies reside. To have the installed packages' binaries available everywhere, you'd then add the `~/.composer/vendor/bin` folder to your PATH.