Download the PHP package rollerworks/monolith-versions without Composer

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

Composer MonolithVersion

This Composer plugin enforces all to-be-installed packages of a monolith versioned distribution to have the same version.

This library is in early development, use at your own risk!

[!NOTE] This will only work with monolith versioned distributions.

Only packages that would be normally installed are enforced to have the same version. Packages that are not installed are not enforced.

For example, if you have a monolith versioned distribution with the following packages:

All the rollerworks/search-* packages should have the same version to ensure proper compatibility between them. While Composer always installs the latest possible version of a package, you might want to ensure all packages are the same version.

Possible scenarios where this is useful:

You want to test that all packages are compatible

The rollerworks-search-doctrine-orm package also installs the rollerworks/search-doctrine-dbal package, which depends on doctrine/dbal. When the doctrine/dbal is not compatible with the latest version of the rollerworks/search-doctrine-dbal package, an older version of the rollerworks/search-doctrine-dbal package will be installed. Which would go unnoticed.

Testing with --prefer-lowest

When testing with --prefer-lowest you don't want to add all sub-packages to the require section, yet you want to ensure the packages are the same version.

Usage

Before installing the plugin, make sure you have the latest version of Composer installed.

Enabling the plugin

Because plugins are disabled by default, you need to enable this plugin before usage.

Install the plugin:

Configuring the plugin

Add the following to your composer.json file (in the extra section):

For example:

Each entry in the monolith-versions array is a monolith configuration, where the key is the name of the monolith and the value is an array with the following keys:

  1. package (required) – The pattern to match the package names against (multiple patterns are allowed using an array).
  2. constraint (required) – The constraint to enforce on the matched packages (same as in require).
  3. exclude (optional) – An array of package names to exclude.

A package name can contain a wildcard (search-*, *search, *), or a expand pattern ({core, doctrine-dbal}).

Please take note of the following limitations:

Override constraints using environment variables

If you want to override the constraint for a specific monolith (for example to test a specific version), you can use an environment variable (per configuration) to override the constraint.

Environment Variable Effect
COMPOSER_MONOLITH_ROLLERWORKS_SEARCH Overrides the constraint for the rollerworks-search monolith.
COMPOSER_MONOLITH_ROLLERWORKS_SEARCH_DOCTRINE_DBAL Overrides the constraint for the rollerworks-search-doctrine-dbal monolith.

This is best used for testing purposes.

Or in a CI environment:

Conflicts when using --with

Using the --with option of the composer update command might not work as expected when a lower version is required than the monolith constraint allows.

Use an environment variable to override the constraint with a more permissive value to resolve this issue.

Like COMPOSER_MONOLITH_ROLLERWORKS_SEARCH="^2.0" composer update --with rollerworks/search:2.1.

Contributing

This is an open source project. If you'd like to contribute, please read the Contributing Guidelines. If you're submitting a pull request, please follow the guidelines in the Submitting a Patch section.

About Us

This library is brought to you by Sebastiaan Stok (@sstok) and supported by [contributors][9].

All versions of monolith-versions with dependencies

PHP Build Version
Package Version
Requires php Version >=8.1
composer-plugin-api Version ^2.1
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 rollerworks/monolith-versions contains the following files

Loading the files please wait ...