Matthieu Moquet (@MattKetmo) - Personal Pages

[...] all your dependencies? That’s easy, just add the vendor name as argument to the update command: This will only install or update the library (plus its dependencies) and overwrite the [...]

[...] . To host the manifest.json file, we will use GitHub pages. Here is what look like our update command: Only two lines of code. Awesome, right? The first parameter of the update method is the [...]

[...] ; we use chmod to make it executable by default; and of course the stub must be enabled for a CLI app. Finally you may wonder what the git-version stands for. The value of this parameter is used to [...]

[...] into its home directory: Then change its default shell: Now you can proxify any git repository from your shell by simply running: The result with the Symfony repository: It takes [...]

[...] source files. Here, any string @package_version@ is replaced by a version number based on the git repository. To take advantage of this, we place it as the version parameter on our main launcher bin/ [...]

[...] ? ». Don’t panic! This is what you should expect if you just have edited the composer.json file. For instance, if you add or update a detail like the library description, authors, extra [...]

[...] ;ve set up your server to point on the root directory of Broker, you could had it to your composer.json file: I would recommend this method which is much easier than the previous one, and also much [...]

[...] also for CI systems (Jenkins/Travis), or PaaS solution like PagodaBox or Heroku which run a composer install each time you deploy a new code. As Git is a decentralized system, it is relativly easy to [...]

[...] — slides Main purpose of this talk was to demonstrate how to build an event-driven PHP application. You may know how NodeJS works via its “Event Loop” to get non-blocking IO. Here [...]

[...] have to add the Satis URI in your composer.json: Using Broker I recently discovered Broker, a PHP application which creates a full repository proxy for Composer. Like the previous method, you have to [...]

[...] Broker, a PHP application which creates a full repository proxy for Composer. Like the previous method, you have to initialize your proxy with the desired vendors before running a composer install [...]

[...] vendor for your project, you can manually add a new line into your composer.json then use the previous method to only install this vendor. But there is a much convenient way to proceed. The require [...]

[...] for Composer. However, keep in mind to update your proxy repositories first before running a composer update. The missing option Both of the previous methods work, but they have the same major [...]

Note: I started to write this article some months ago but I never took the time to finish it. So, it's not really "fresh" news, but nonetheless, there [...]