Download the PHP package zfcampus/zf-asset-manager without Composer
On this page you can find all versions of the php package zfcampus/zf-asset-manager. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download zfcampus/zf-asset-manager
More information about zfcampus/zf-asset-manager
Files in zfcampus/zf-asset-manager
Package zf-asset-manager
Short Description Composer plugin for copying module assets into application document roots.
License BSD-3-Clause
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 zf-asset-manager
zf-asset-manager
Repository abandoned 2019-12-31
This repository has moved to laminas-api-tools/api-tools-asset-manager.
zf-asset-manager is a composer plugin that will copy configured web-accessible assets into the public document root of your Zend Framework application. It uses the configuration format of rwoverdijk/AssetManager, and specifically the subset:
Each configured path is iterated, and every path under it is then copied into the public tree.
Installation
Recommended for development
We recommend usage of this module primarily for development purposes. In most cases, assets from third-party modules should be overridden with project-specific assets when preparing for production. To emphasize this, the assets are excluded from your git repository by default. (You may add them manually later, as explained below.)
Example
As an example, given the following directory structure inside a package:
where module.config.php defines (minimally) the following:
When you install the package, the asset manager will copy each of the
asset/zf-apigility/ and asset/zf-apigility-welcome/ trees to the project's
public/ path. The individual files asset/README.md, asset/gruntfile.js, and
asset/package.json are omitted from the install, as they are not directories.
Additionally, during installation, the plugin adds a .gitignore file to the
public/ path, listing each of the new directories:
After installation, you may access any of the assets installed relative to the public root.
Uninstallation
When you remove the module, the plugin will:
- Remove any asset trees configured for the module from the public tree.
- Remove the
.gitignoreentries associated with those asset trees from thepublic/.gitignorefile.
Keeping assets
Assets are marked by Git to ignore by default. The intention of this module is primarily for development purposes; it was developed to allow installation of assets related to the Apiglity admin UI, welcome screen, and documentation, most of which are relevant in development mode only.
However, if you wish to keep the assets in your public tree, you can do so as follows:
- Edit the
public/.gitignorefile to remove the entry for the asset tree(s) you wish to keep. - Add the asset tree(s) to your repository (
git add public/{tree}).
Removing the entry from public/.gitignore is enough to prevent the uninstaller
from removing the assets when you remove a module.
All versions of zf-asset-manager with dependencies
composer-plugin-api Version ^1.1