Download the PHP package andkirby/multi-repo-composer without Composer

On this page you can find all versions of the php package andkirby/multi-repo-composer. 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 multi-repo-composer

Multi-package repository for Composer

Gitter This repository contains multi-package composer repository and GitLab repository for composer.

Released v0.9.x. It supports generating "dist" config for packages. Satis may provide links to archives.

Requirements

Package Name

You have to name your packages by name format: vendor/my_repo-package_name Where package_name - your namespace in GIT.

Naming

Please be aware "-" is namespace separator in first case. A package with name me/foo-cool_package-second_edition will produce a multi-repo directory:

foo - is a base repository name in this example.

That's why you SHOULD NOT use "-" in the name spaces.

Branch Name and Tag Name

Branch and tag should have a namespace like PackageName/branch. Examples:

Single GIT repository in vendor

If you require several packages from your multi-repository it will create the one with GIT (if you use vcs). The name by example is vendor/myrepo-multi-repo. Ie your general repository name + -multi-repo. It's just to avoid clone a repository several times.

Satis

andkirby/satis is modified version of composer/satis with supporting multi-repositories.

GIT Flow

You may follow GIT Flow.

Configuring

Default multi repositories path

Actually multi-repositories will be placed in the repositories cache directory:

Custom multi-repositories directory

But you may customize it via root configuration below:

Current vendor multi-repositories directory

Also you may use saving in the current vendor directory.

It will have following structure:

GitFlow

Probably it would be useful to switch a namespace in GitFlow quickly. Try to use composer package rikby/gitext

Manual way

Create a file .git-flow-namespace-set.sh

And then add an alias

Now you may use it:

All versions of multi-repo-composer with dependencies

PHP Build Version
Package Version
Requires composer-plugin-api Version ^1.0.0
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 andkirby/multi-repo-composer contains the following files

Loading the files please wait ....