Download the PHP package evozon-php/composer-utilities without Composer

On this page you can find all versions of the php package evozon-php/composer-utilities. 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?

Example code of evozon-php/composer-utilities

Informations about the package composer-utilities

Composer Utilities

Different Composer utilities for various use cases.

Installation

Synchronize composer.json

When working on a monolith repository, you might have different .json files.

In this case, there might one .json file for development (i.e. dev.json) which installs from local repositories and maybe also different releases. Another .json file (i.e. composer.json) would be used for installing packages from remote repositories and probably stable versions.

Add the following to your source .json file:

All you need to do is to define the nodes you want to ignore during synchronization. Make sure you define them in PropertyAccess format.

The plugin will hook automatically to the post-install-cmd and post-update-cmd events and ask if you want to synchronize.

This will work only if you specifically use a custom .json file:

There is also a custom command added when you want to manually trigger the synchronization process:

Force Update Parameters

Useful when some parameters change in parameters.yml.dist but updating them parameters.yml is tedious. Usually it's the case with array parameters.

Add the following to your composer.json file:

The plugin will hook automatically to the post-install-cmd and post-update-cmd events and ask if you want to update parameters.

There is also a custom command added when you want to manually trigger parameters update process:


composer parameters:update --source app/config/parameters.yml.dist --target app/config/parameters.yml

All versions of composer-utilities with dependencies

PHP Build Version
Package Version
Requires php Version >=7.1
composer-plugin-api Version ^1.1
symfony/console Version ^4.0
symfony/property-access Version ^4.0
symfony/filesystem Version ^4.0
symfony/yaml Version ^4.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 evozon-php/composer-utilities contains the following files

Loading the files please wait ....