- How do I install jrm2k6/cloudder in a Laravel 5 app?
- Run composer require jrm2k6/cloudder on a Laravel 5.x application. Register the package service provider in config/app.php and add the Cloudder facade alias, since early Laravel 5 releases do not support package auto-discovery. Publish the cloudder.php config file with php artisan vendor:publish, then set your Cloudinary cloud name, API key, and API secret, preferably through environment variables.
- Does Cloudder support Laravel 6, 8, or 9?
- Cloudder targets Laravel 5.x. On Laravel 6 and later compatibility degrades, and on Laravel 9+ it is effectively unusable without forking because the package is archived and pins an older Cloudinary PHP SDK. If you are upgrading Laravel, plan to replace Cloudder with the official SDK or a maintained Cloudinary integration.
- How do I configure Cloudinary credentials with Cloudder?
- After publishing cloudder.php, fill in the cloud name, API key, and API secret from your Cloudinary account. Keep these values out of source control by reading them from .env in the config file. Verify that your Cloudinary upload presets and signed or unsigned upload settings match what the wrapper expects.
- What can I do with the Cloudder facade?
- The Cloudder facade proxies to the Cloudinary PHP SDK, so you can upload images and videos, apply transformations, tag assets, and delete media from controllers, jobs, or Blade views. It is a convenience wrapper, not a storage abstraction, so Cloudinary-specific method calls will be visible in your application code. Wrap those calls in an internal adapter if you want to limit coupling.
- Is jrm2k6/cloudder still maintained or safe for production?
- Cloudder is archived and receives no security patches, so production use carries high risk, especially because credentials and upload endpoints are sensitive. The pinned Cloudinary SDK and Guzzle versions may also drift from current APIs and PHP 8 type signatures. For maintained applications, use the official cloudinary/cloudinary_php SDK or a maintained Laravel package behind your own interface.
- How do I mock the Cloudder facade in tests?
- Mocking a facade that proxies to a vendor SDK is brittle because you end up faking static calls and SDK behavior. The safer approach is to introduce a small MediaUploader interface, implement it with Cloudder today, and inject that interface into controllers and jobs so tests can use a simple fake. If you must mock the facade, use Laravel's facade swapping utilities, but expect the tests to need updates when you migrate.
- How do I migrate from Cloudder to the official Cloudinary PHP SDK?
- Start by containing Cloudder behind an internal adapter such as MediaUploader, and route all new code through it. Then install the official Cloudinary PHP SDK, reimplement the adapter against it, and run both paths behind a config flag during rollout. Once parity is verified, remove Cloudder call sites, the facade alias, and the cloudder.php config.
- Does Cloudder work with PHP 8 and modern Guzzle?
- Likely not without changes. Cloudder is archived and constrains an older Cloudinary PHP SDK, which can conflict with PHP 8 type signatures and current Guzzle or PSR-7 versions. Before committing, verify the PHP version supported by the pinned SDK and align Guzzle with the rest of your dependency graph.
- Can I use Cloudder with S3, local disk, or Flysystem?
- No. Cloudder is a thin syntactic wrapper around Cloudinary, not a Flysystem or S3-style storage driver, so it does not provide a storage-agnostic interface. If your application needs swappable media storage, define your own interface and treat Cloudinary as one implementation. That seam is also the cleanest path away from the archived package.
- What are alternatives to jrm2k6/cloudder for Laravel?
- The primary alternatives are the official cloudinary/cloudinary_php SDK and a maintained Cloudinary Laravel integration, both wrapped behind a small internal MediaUploader interface. For Laravel 5.x in maintenance mode, keeping Cloudder contained may cost less than an immediate rewrite, but new projects should not adopt it. Evaluate package maintenance status and Laravel version support before choosing.