Download the PHP package yosymfony/embedded-composer without Composer
On this page you can find all versions of the php package yosymfony/embedded-composer. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download yosymfony/embedded-composer
More information about yosymfony/embedded-composer
Files in yosymfony/embedded-composer
Package embedded-composer
Short Description Embed Composer into another application
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package embedded-composer
Embedded Composer
Embed Composer into another application. This library is based on dflydev-embedded-composer. Due to this latter seems abandoned, I decided to fork this one and start my own way.
Why Would I Want To Embed Composer?
Imagine a console application shipped as a phar. If it is desired for the
application to be extensible based on which directory it is in (say one set
of plugins should be used in one directory but an entirely different set of
plugins used in another directory) one cannot simply define a composer.json
in both directories and run composer install.
Why not? Because the application shipped with a specific set of dependencies.
Composer cannot add more dependencies without running the risk of introducing
conflicts. The answer is to embed Composer into the application so that
Composer can merge the dependencies already installed for the application
with the dependencies defined in a specific directory's composer.json.
The end result is a set of dependencies that satisfy the directory specific requirements while taking into account the dependencies already installed for the console application.
While this is required for a phar distributed application this technique can be applied to any globally installed application that needs to be runtime extensible.
Usage
Basics
The following is an example bin/myapp style script that can be used either
installed via Composer (vendor/bin/myapp) or installed globally
(/usr/local/bin/myapp).
myapp.php (bin)
A shared block of code to initialize Embedded Composer from an application.
myapp (bin)
Example bin script (bin/myapp) that requires the shared block of code
after it locates the correct autoloader.
myapp-phar-stub (bin)
Example phar stub (bin/myapp-phar-stub) that can be used to bootstrap
a phar application prior to requiring the shared block of code.
What else ...
Find installed package by name
One can search for any package that Composer has installed by using
the findPackage method:
Create a Composer instance
Create a Composer Installer instance
The Installer instance is suitable for processing install and update
operations against the external configuration. It will take the internal
(embedded) configuration into account when solving dependencies.
