Download the PHP package wearejh/statics-merger without Composer
On this page you can find all versions of the php package wearejh/statics-merger. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download wearejh/statics-merger
More information about wearejh/statics-merger
Files in wearejh/statics-merger
Package statics-merger
Short Description A composer plugin that symlinks static assets into the JH Magento Skeleton
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 statics-merger
Statics Merger
A composer plugin aimed to simplify the workflow between the frontend and backend development teams. Static repositories that the frontend team use are added as a composer dependency to the project as type .
The plugin hooks onto two composer commands and in which on completion will symlink all static packages as defined in their file.
Installation
This module is installable via . If you have used the Magento Skeleton as a base module then you can just require this project and all the rest is done for you.
Magento 1
Magento 2
Upgrading 1.x to 2.x ?
It's recommended to first run composer update statics-merger --no-plugins after changing your composer.json and then run a composer update nothing to map the new configuration.
Note: Depending on the configuration changes you may also have to manually cleanup any remaining symlinks from the old mappings
Usage
Statics project
If the composer.json file is not already there, create one with relevant information and commit it to the repo.
For this to work the statics repository requires the composer.json to have the type set to static.
Example Static Composer.json
Magento project
Within your projects composer.json you will need to ensure you have a few configurations set up.
In your require you will need to add any statics that you want and if private also add the repo.
Note: It's great at handling multiple static repositories :thumbsup:
In your you need the set correctly and have defined the for each static repository.
The first key is the name of the repository which you have used in the require section, while inside there each key is the package/theme in which the example would map to skin/frontend/package/theme within your `magento-root-dir.
The package/theme array contains several objects defining the src and dest of the files. The src value is relevant to the root of the statics repository while the dest is relevant to the package/theme defined in the Magento project such as skin/frontend/package/theme/ within your magento-root-dir.
Need to map a static repo to more than 1 package or theme? No problem just add another package/theme array to your repos mappings, of course make sure you use a different name to any others to avoid overwriting.
Valid Mappings
Note: Globs require the dest to be a folder and not a file, whereas files and directories need to point to there corresponding full path which allows you to rename them if required. If you leave the dest blank on a glob it will map to the same source directory structure within your package/theme
Files
Link an image into a different directory structure and rename
Directories
Linking a whole directory keeping all sub-dirs & files
Globs
You can also use globs which makes it pretty awesome! A great use case for this is favicons where you could have multiple at different resolutions with a set naming convention. To target them all you would simply use favicon* like in the default example below.
All favicons to root dir skin/frontend/package/theme/
Final Notes
- Use tags to explicitly pull in the static repositories
- Don't forget to add the
package/themedir to your.gitignoreotherwise you will add the statics files to the Magento repo, and everyone will hate you - You can amend statics directly from the
vendordir and push straight to the main repo, WIN! - Have fun !! :smile:
Problems?
If you find any problems or edge cases which may need to be accounted for within this composer plugin just open up an issue with as much detail as possible so it can be recreated.
