Download the PHP package meeva/composer-monorepo-builder-path-plugin without Composer

On this page you can find all versions of the php package meeva/composer-monorepo-builder-path-plugin. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

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 PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • 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.
Please rate this library. Is it a good library?

Informations about the package composer-monorepo-builder-path-plugin

monorepo-builder-path (composer plugin)

Composer plugin intended to use in conjunction with symplify/monorepo-builder.

When having a repository of kind:

where example1 has dependencies to monorepo/subproject1 you may like to install vendors, while keeping only a single copy of your subproject1. Symlinks aka. Path-Repositories to the rescue!

This also allows you to use the dependency before even publishing it to an external, without manually adding the path-repository to your composer.json

Usage

composer global require meeva/composer-monorepo-builder-path-plugin

That's all. Nothing to configure. It detects your monorepo_dir by traversing up to your merged composer.json, and search all other composer.json in subdirectories (vendor excluded).

Now if you do composer require monorepo/subproject1 within the path monorepo_dir/projects/example1 it should use a path-symlink to install the dependency to monorepo_dir/projects/example1/vendor.

Deployment

Assuming you're gonna build a deploy version of your Project, this plugin is disabled if you're using --no-dev.

Also you can use the environment-variable COMPOSER_MONOREPO with one of these values:

Known Caveats

All versions of composer-monorepo-builder-path-plugin with dependencies

PHP Build Version
Package Version
Requires composer-plugin-api Version ^2.0
php Version >=7
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package meeva/composer-monorepo-builder-path-plugin contains the following files

Loading the files please wait ....