Download the PHP package lastcall/composer-upstream-files without Composer
On this page you can find all versions of the php package lastcall/composer-upstream-files. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download lastcall/composer-upstream-files
More information about lastcall/composer-upstream-files
Files in lastcall/composer-upstream-files
Package composer-upstream-files
Short Description Composer command to update application files from various upstream sources.
License MIT
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-upstream-files
Composer Upstream Files Plugin
Composer Upstream Files Plugin is brought to you by your friends at Last Call Media, this Composer plugin allows you to update files belonging to your application from various upstream sources. There are a couple of different use cases for this:
- You have files that are required for specific versions of your application dependencies, but which need to live as part of your application. For example, Drupal's
index.phpfile is required, but must live outside of thecoredirectory when you use a Composer based installation. - You have files you want to allow modifications to (so they're not appropriate for inclusion in a library), but that you want to keep in sync between different projects. For example, a default
.eslintrcorphpcs.xml.dist.
In all cases, the files that would be managed by this plugin should be committed to the application's repository. This plugin does not automatically update these files - it only provides a Composer command you can use to update them -- you should do this periodically, then review and commit the resulting changes.
Installation
Install this plugin in your application with Composer:
Usage
Upstream files are defined in the extra section of your composer.json. Example:
In this example, we've defined two files with upstream sources. The key of the files array is the source, and the value is the destination. When we run composer upstream-files:update, both files will be refreshed from their respective URLs. We would then review and commit the changes.
Tokens
This plugin supports using tokens to reduce the amount of stuff you have to type and update. Tokens are enclosed in double brackets. Example:
You can define any tokens you want to use under the tokens key, and use them as replacements for your files. Additionally, you can reference the current version of any installed package by using {{PACKAGENAME.version}} (as we did with drupal/core above). Tokens are replaced recursively, so if your token contains a token, that's fine.
Manifests
You can also reference "manifests", or JSON files that contain an upstream-files specification. These manifests can be local or remote. See this example:
Manifests can also specify other manifests, which is handy when you need to specify a lot of files.
Exclusions
It is also possible to exclude files based on their source or destination. This is most useful when you use manifests from upstream projects, and don't want to pull in certain files from upstream:
The sourceExcludes and destinationExcludes properties are both arrays of regular expressions indicating the files you wish to exclude. sourceExcludes will be matched against the fully resolved source URL, and destinationExcludes will be matched against the fully resolved destination path.
