Download the PHP package steady-ua/unicorn without Composer

On this page you can find all versions of the php package steady-ua/unicorn. 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 unicorn

unicorn

The composer plugin organizes a mono-repository of php packages.\ Ensures the consistency of all dependencies on the same package version.\ Adds tools for working with shared dependencies.

  1. Concept
  2. Installation
  3. Usage
  4. Commands
  5. The unicorn.json shema

Concept

For example, we have two projects:

Both projects use common packages placed in the packages directory

composer - provides the ability to include local packages by specifying your own path repository.\ But there are a number of limitations, such as:

The steady-ua/unicorn plugin removes these restrictions and provides tools for analyzing and updating dependencies.

In the root folder, you need to place the unicorn.json file. It describes all the common repositories.

Optionally, other types of private repositories can be specified.

Now any local package can include packages from these repositories.\ No more need to describe the path repositories in each package.

A shared folder uni_vendor is created where all required packages are installed.\ All dependent packages create symbolic links to them.

This is to ensure that all dependencies use the same version.\ And it speeds up installation.

The used versions are fixed in the unicorn.lock file and will be used during installation.

When deploying an application, instead of symbolic links, you can copy the necessary packages.\ Command composer uni:build

Installation

Compatible with composer version 2.3 or later.\ Currently does not work on windows operating system.\ The plugin must be installed globally.

Usage

After creating the unicorn.json file, just use composer as usual.

The unicorn.lock file is recommended to be kept under a version control system (eg GIT). The uni_vendor directory, like the vendor directories, is recommended to be excluded. The generated composer.lock files should also be excluded.

If a version conflict occurs when including a dependent package, an error will be displayed.

Use next commands to solve problems.

Commands

composer uni:install

composer uni:install [options] [--] [<packages>...]

When called without parameters. If the uni_vendor directory does not exist, install all dependencies. Otherwise, it will check the consistency of package requirements.

You can specify a list of local packages. In this case, for each package, the command will be executed composer install

composer uni:update

compose uni:update <packages>...

Update required packages in all dependents.

With this command, you can also change the constraint. e.g. foo/bar:^1.0 or foo/bar=^1.0 or "foo/bar ^1.0". This will edit the composer.json files.

During the execution, the composer.json files will be changed.\ In case of an error, the files will be returned to their original state.

Additionally, you can specify a list of scripts that will be executed after the changes.

composer uni:version

uni:version [ major | minor | patch ]

Bump version of package.

Upgrades a package and updates all dependencies.

During the execution, the composer.json files will be changed.\ In case of an error, the files will be returned to their original state.

Additionally, you can specify a list of scripts that will be executed after the changes.

composer uni:run

uni:run [options] [--] [<script>...]

Runs the scripts defined in unicorn.json, for all packages dependent on the current.

Options:

composer uni:why

Shows which packages cause the given package to be installed.

composer uni:why-not

Shows which packages prevent the given package from being installed.

composer uni:show

Shows information about packages.

composer uni:namespace

Suggest package by namespace pattern.

composer uni:build

composer uni:build <package> <directory>

Builds a local package in the specified directory. All required packages will be copied instead of symlinked.

It is possible to set options for executing the command composer install

The unicorn.json schema

Located at the root of the mono-repository.

repositories

Custom package repositories to use.

The format is the same as Composer

Example:

You can group packages into subdirectories.\ Then the url will be like this "url": "./packages/*/*"

extra

build-install-options

Type: string

Additional options to be passed to the command composer install for uni:build

Example:

post-update-scripts

Type: array

The name of the scripts that will be executed for all changed packages during the execution of commands: uni:version.

Example:

All versions of unicorn with dependencies

PHP Build Version
Package Version
Requires php Version >=8.0
ext-json Version *
symfony/console Version ^5.0|^6.0
composer/composer Version ^2.3
composer-plugin-api Version ^2.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 steady-ua/unicorn contains the following files

Loading the files please wait ....