Download the PHP package dmcblue/php-image-resize without Composer
On this page you can find all versions of the php package dmcblue/php-image-resize. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
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 php-image-resize
php-image-resize
A convenience tool to resize a batch of images into different sizes for website asset responsiveness.
Requirements
- PHP 7+
- PHP GD image module
Features
- Resizes images or a folder of images into predefined size sets.
- Two types of resize:
containandcover, think CSS background-size. - Can be configured to prevent enlarging of images, with down sampling only (the default).
- Handles any number of size groups all at once.
- Adds postfixes to the filename.
- Currently handles BMP, (static) GIF, JPG and PNG.
Notes
The code is limited by the allowed memory size designated in php.ini by memory_limit. If php tries to allocate more memory than it is allowed, it will shutdown in the middle of creating a file.
When running the script again, it will run into this truncated file in the output folder and throw the following error:
You just need to delete the file (or better all the output files to be sure) and then run the script again.
I have not found a satisfactory way to detect either of these problems before a shutdown error.
