Download the PHP package jobiqo/composer-patches-install without Composer

On this page you can find all versions of the php package jobiqo/composer-patches-install. 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-patches-install

jobiqo/composer-patches-install

A Composer plugin that detects patches.lock.json changes and automatically triggers re-patching of affected packages. See https://github.com/cweagans/composer-patches/issues/583

This is relevant for sites that use a git pull && composer install workflow. With composer-patches 2.x this is not sufficient anymore to get any patches.lock.json changes installed. The workaround is git pull && composer install && composer patches-repatch, but has downsides:

What it does internally

  1. On a fresh install (no vendor/ directory), pre-initialises the patches.lock.json cache so the first composer install does not trigger unnecessary reinstalls.
  2. On subsequent composer install, compares patches.lock.json against the cached copy in vendor/composer/patches.lock.json.
  3. Re-installs only the packages whose patch hashes have changed, so patches are always applied consistently.
  4. Supports --no-dev mode: dev-only packages are skipped when running without dev dependencies.

Requirements

Installation

Usage

Generate a patches.lock.json file with composer-patches in the root of your project (next to composer.json). The plugin reads the patches key and its sha256 hashes (as written by cweagans/composer-patches v2) to decide which packages need to be reinstalled.

Run composer install and patch changes will be picked up automatically.

All versions of composer-patches-install with dependencies

PHP Build Version
Package Version
Requires php Version ^8.1
composer-plugin-api Version ^2.0
cweagans/composer-patches 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 jobiqo/composer-patches-install contains the following files

Loading the files please wait ...