Download the PHP package hongliang/alterload without Composer
On this page you can find all versions of the php package hongliang/alterload. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download hongliang/alterload
More information about hongliang/alterload
Files in hongliang/alterload
Package alterload
Short Description An alternative loader to autoload
License MIT
Homepage https://github.com/h-wang/alterload
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 alterload
Alterload for Composer
Why Alterload
Alterload is an alternative loader for autoload.
Alterload is great for library developers. When developing a PHP project/application we use composer to manage dependencies. Sometimes we need to work on a dependency of the project but still need to debug/test in the project. Think of a library that's part of the project.
Before Alterload there were 2 things we could do to debug/test the library in the project:
- Commit new version of the library for all changes, wait for packagist to re-index, and update your composer.lock in the calling project and test.
- Add a "repository" to your calling project's composer.json (which you shouldn't forget to remove during commit, and put back after)
* Symlinking or directly edit files in the vendor directory is not to discuss
Alterload is inspired by https://github.com/linkorb/autotune
How does it work
Making your application ready for Alterload takes 3 simple steps:
1. Include hongliang/alterload from Packagist in your composer.json file
2. Initialize Alterload in your app
Somewhere in your application, you're including vendor/autoload.php. Sometimes it's in web/index.php or bin/console. Find this location, and modify add these lines:
Wrapping the call to alter in the class_exists block ensures alterload is only used if Alterload is installed in your (development) environment (installed from the require-dev block in composer.json). In production environments it won't be called if you install your dependencies with --no-dev)
3. Add an .alterload.ini file to your project root.
Ideally you'd add the .alterload.ini to your .gitignore file.
Done
Whenever your application is doing something like the following, it will load the "local" version of a library, instead of the one in your vendor/ directory.
So from now on, no changes are required to your main application. Everything is managed by your local .alterload.ini file.
Symlink a dependency
Sometimes we also want to use other assets (templates, js, images,...) in the depending library instead of only the PHP classes. In this case we can use the vendor/bin/alterload link command to symlink a library (in the vendor directory) to the local library.
Simply add link: in front of the .alterload.ini line:
Then run the command from your application directory:
License
MIT (see LICENSE.md)
