league/glide-laravel
Laravel adapter for League Glide image server. Easily serve on-the-fly resized, cropped, and optimized images using Glide within Laravel. Install via Composer and configure Glide to handle image requests with caching and storage support.
Architecture fit is poor for modern Laravel applications due to the package's last release in 2015. Current Laravel versions (8+) rely on Flysystem v2+ and PSR-7 standards, while this adapter likely uses deprecated service providers and facades. Integration feasibility is low – testing with Laravel 9/10 would likely reveal breaking changes in dependency resolution and service container binding. Technical risks include unpatched security vulnerabilities (no updates since 2015), PHP 8+ incompatibility, and potential conflicts with Laravel's native image handling. Key questions: Why does this package exist when the core league/glide (actively maintained) works seamlessly with Laravel's filesystem abstraction? Is there an official migration path from this adapter to direct Glide usage?
Stack fit is incompatible with current Laravel ecosystems. Modern Laravel applications should use league/glide directly via Flysystem integration rather than this deprecated adapter. Migration path would require removing this package and implementing Glide via Laravel's native Storage facade with custom Glide server configuration. Compatibility is broken for PHP 7.4+ and Laravel 6+ due to missing type declarations and deprecated Symfony components. Sequencing should avoid this package entirely – instead, adopt the official Glide documentation for Laravel integration which uses simpler filesystem bindings without a dedicated adapter.
Maintenance burden would be high due to unmaintained codebase requiring custom fixes for every Laravel upgrade. Support is nonexistent – GitHub issues are closed without response and no active maintainers. Scaling is risky as image processing failures could cascade due to unpatched concurrency issues in legacy code. Failure modes include fatal errors from missing class/method signatures in newer PHP/Laravel versions and security vulnerabilities in outdated dependencies (e.g., Symfony components). Ramp-up would be unnecessarily complex as developers would need to debug compatibility issues rather than leveraging Laravel's built-in Flysystem integration documented in current Laravel docs.
How can I help you explore Laravel packages today?