Download the PHP package clearlyip/composer-push without Composer
On this page you can find all versions of the php package clearlyip/composer-push. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download clearlyip/composer-push
More information about clearlyip/composer-push
Files in clearlyip/composer-push
Package composer-push
Short Description Provide a Push command to composer to push to repositories
License Apache-2.0
FAQ
Example:
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 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.
Informations about the package composer-push
Push command for composer
This composer plugin provide a composer push command that allow to push the current package into a distant composer repository.
- Note: This is the spiritual successor to https://github.com/Elendev/composer-push
Currently supported repositories are:
- JFrog Artifactory
- Nexus, with nexus-repository-composer.
Installation
Usage
Many of the options are optional since they can be added directly to the composer.json file.
Configuration
It's possible to add some configurations inside the composer.json file
Above configuration may be called unique repository configuration format, as you can only configue one repository in composer.json.
In practice, for security reasons, different versions of component code, such as production and development, often apply different deployment policy, such as disable redeploy for the production version and allow redeploy for the development version, so they need to be stored in different repositories. For versions later than 0.1.5, the command-line parameter -- repository is introduced to meet this requirement. To enable the -- repository parameter, the composer.json file needs to be in the following format:
Above configuration may be called multi repository configuration format.
The new version continues to support parsing the unique repository configuration format, but remember that you cannot use the -- repository command line argument in this scenario.
The username and password can be specified in the auth.json file on a per-user basis with the authentication mechanism provided by Composer.
Providers
Specificity for some of the providers.
Nexus
Source type, URL, reference
This is an optional part that can be added to the composer.json file provided for the package which can contain the source reference for this version. This option is useful in case you have a source manager and you would like to have a direct link to the source of an specific version. The example above given will read the last commit ID from git and the remote address from git as well which is quiet simple and useful.
Artifactory
Tokens
Tokens are currently supported when used as password. The username is still required for it to work.
Standalone tokens are currently not supported.
Example of token usage:
All versions of composer-push with dependencies
ext-curl Version *
ext-zip Version *
composer-plugin-api Version ^2.0
guzzlehttp/guzzle Version ^7.0
symfony/finder Version ^6.0 || ^7.0
symfony/filesystem Version ^6.0 || ^7.0