- How do I install onigoetz/imagecache in a Laravel application?
- Install it with Composer, then publish and adjust the package configuration and service provider wiring as needed. The package is expected to avoid database migrations, but you will need to define image sources, route configuration, and URL construction at call sites. Confirm the Composer constraint resolves cleanly in each target Laravel app before committing.
- Which Laravel and PHP versions does onigoetz/imagecache 3.2.0 support?
- Version 3.2.0 supports only Laravel 11 and 12 after dropping end-of-life Laravel versions. Your PHP version must satisfy both the Laravel framework and the package constraints, so verify resolution in each application. Treat the version floor as a hard break rather than relying on a caret constraint to protect older apps.
- What does onigoetz/imagecache actually do?
- It generates manipulated image derivatives on demand and caches them, typically through a route or helper that accepts a source image plus transform parameters such as dimensions, crop, and quality. Cached files are stored on the local or configured filesystem disk, and the original images remain untouched. It is not an upload manager, media library, or editorial workflow tool.
- How are image presets and URL-based filters configured in onigoetz/imagecache?
- You define reusable templates or presets and apply URL-based filters and resizing parameters when requesting a derivative. Typical integration involves publishing the config, defining image sources and routes, and building URLs through a Blade helper or manual URL construction. Keep presets constrained rather than allowing arbitrary transform values from public requests.
- Where should the onigoetz/imagecache cache live in production?
- Use a cache location that matches your deployment topology: local disk for simple single-node setups, a shared volume for a few nodes, or object storage such as S3 for elastic or containerized environments. Ephemeral local filesystems are a poor fit because cache misses and lost derivatives will recur. The cache should be persistent and reachable by every web tier that serves transformed images.
- Can I use onigoetz/imagecache with S3 or object storage?
- The package caches derivatives on the local or configured filesystem disk, so pointing that disk at S3 or similar object storage is the relevant approach. Verify your Laravel filesystem configuration, latency expectations, and whether every node can access the same cache. Avoid using container-local ephemeral storage if instances are replaced frequently.
- Is onigoetz/imagecache safe for publicly exposed image URLs?
- Publicly addressable, parameter-driven image transformation is a classic amplification and denial-of-service vector through arbitrary dimensions, repeated cache misses, oversized sources, and decompression bombs. Add explicit guardrails such as allowlisted sizes, signed or expiring URLs, rate limiting, and maximum source dimensions. Do not assume the package natively provides all of these controls; wrap it where necessary.
- Does onigoetz/imagecache support WebP, AVIF, or animated GIF?
- The provided context does not confirm format-specific support, so capability will depend on the image driver, such as GD versus Imagick, and the package's handling. Test the exact formats you need, including WebP or AVIF negotiation and animated GIF behavior, before adopting it. Confirm driver support in the same PHP environment you will run in production.
- How should I test an application using onigoetz/imagecache?
- Cover the transform route or helper, cache hits and misses, and the configured filesystem disk behavior in your test suite. Assert that originals remain untouched and that invalid, oversized, or unexpected transform parameters are rejected or safely bounded. Run those tests on the Laravel 11 or 12 version and PHP image driver used in production.
- What alternatives to onigoetz/imagecache should I consider?
- Alternatives include a dedicated image CDN such as Cloudinary, imgproxy, or Fastly IO, existing intervention/image calls in controllers, and pre-generated derivatives. A media library such as spatie/laravel-medialibrary complements rather than replaces this package when you need uploads, metadata, or editorial workflows. Because onigoetz/imagecache is effectively single-maintainer, keep a fork or replacement plan if releases stall.