Download the PHP package soyuka/pmu without Composer
On this page you can find all versions of the php package soyuka/pmu. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
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 pmu
PMU
PMU (PHP Monorepo Utility) is a Composer plugin specifically designed to facilitate PHP monorepo management. It provides commands for running operations on single or multiple projects, synchronizing dependencies, and blending shared configurations. PMU simplifies dependency handling and automation across interconnected packages, ensuring efficient development and maintenance in monorepositories.
Installation
Configuration
Note that repositories are propagated to each project when running commands from the base composer.json file. An example is available in the tests/monorepo directory.
Commands
Run a command on a single project
For example: composer test/a install.
Run a command on every projects
Runs composer install on every projects.
For example to change the branch alias:
Blend dependencies
Blend your root composer.json constraints in each of the projects.
Note: there's no dry mode on this command, use a VCS to rollback on unwanted changes.
When project-a depends on dependency-a:^2.0.0 and your root project has dependency-a:^3.0.0, running composer blend will set the requirement of dependency-a to ^3.0.0 in project-a.
We do not check if a dependency is valid, you should probably run composer all validate or composer all update after running this.
Blend can also transfer any json path:
Or blend a given value:
Where force will write even if the value is not present in the project's composer.json.
When you want to bump all your mono-repository's dependencies and ignore the rest use --self, this is quite handy with the --all option, on API Platform we use this to align every dependency of our mono-repository (eg: set every version to the ones defined on our root composer.json):
Run a graph of dependencies
Example: composer graph test/a to see the dependencies for the test/a project.
Checks dependencies
This script reads the code and detect use classes. It then checks that the dependencies are correctly mapped in the require or require-dev of each project.
Link
To link your project's mono-repository dependencies use composer link. This will create a temporary composer definition with:
- configured repository on each project's
path - add a
@devconstraint to force composer to run local symlinks - run
composer update - revert the definition to the previous ones (we recommend running this command after setting up a version control system)
You can run this command on a global install to link a directory to the current project:
TODO:
- create and
affectedgraph to be able to run tests on affected projects
