Weave Code
Cloudinary Bundle Laravel Package
speicher210/cloudinary-bundle
Symfony bundle that integrates Cloudinary's cloud-based image and video management into your app, providing service configuration, upload and transformation helpers, and template integration for serving optimized, responsive media.
Speicher210 CloudinaryBundle integrates the Cloudinary PHP SDK into Symfony applications, providing a configurable way to manage media assets without manually wiring the SDK. Configure your Cloudinary credentials once and use the bundle’s services to upload images, generate transformation URLs, and deliver optimized assets.
- Registers Cloudinary services in the Symfony DI container
- Configures API credentials through bundle configuration
- Exposes SDK upload and asset capabilities
- Simplifies transformation and delivery URL generation
- Follows standard Symfony bundle workflows
Frequently asked questions about Cloudinary Bundle
- Can I use speicher210/cloudinary-bundle in a Laravel application?
- Not natively. It is a Symfony bundle with a DI extension, Twig extension, and Symfony console commands, so a Laravel app cannot load its service wiring or call its Twig filters without an adapter. The Cloudinary client factory logic and command bodies are portable, but you would own a CloudinaryServiceProvider and Blade components. Treat it as a reference implementation rather than a drop-in Laravel package.
- How do I install speicher210/cloudinary-bundle with Composer?
- Run composer require speicher210/cloudinary-bundle, but expect Symfony-style registration rather than Laravel package discovery. In Symfony you enable the bundle in bundles.php; in Laravel you would need to write a service provider that binds the Cloudinary clients from config. Before installing, confirm the published artifact matches the tagged commit because the listed release date is 2026-09-26, which is a metadata red flag.
- Does speicher210/cloudinary-bundle support Laravel 10, 11, or 12?
- There is no published Laravel support matrix because this is a Symfony bundle, not a Laravel package. Laravel version compatibility is therefore something you create through an adapter, not something the package guarantees. Laravel shares Symfony Console and EventDispatcher components, so command code is salvageable, but the container and Twig layers are not. Test any port against your exact Laravel and PHP versions.
- How do I configure Cloudinary credentials in Laravel with this bundle?
- The bundle configures Cloudinary through a Symfony DI extension, so its configuration will not load automatically in Laravel. The practical path is to create config/cloudinary.php, copy the bundle's configuration schema concept, and bind the Cloudinary, admin API, and upload API clients in your own service provider. Keep credentials in environment variables and avoid committing cloud name, API key, or API secret.
- Can I use the Twig helpers from speicher210/cloudinary-bundle in Blade templates?
- No. The Twig extension that generates asset URLs and img, picture, and video tags is not callable from Blade. Reimplementing those helpers as Blade directives or components such as @cloudinaryImage and x-cloudinary-video is the real porting cost and duplicates the bundle's most distinctive feature. If your codebase is Blade-only, that value proposition largely disappears.
- Does speicher210/cloudinary-bundle provide Artisan commands for uploading or deleting Cloudinary assets?
- It ships Symfony console commands for upload, inspect, and delete, not Artisan commands. Because Laravel uses Symfony Console under the hood, the command bodies can be adapted into Artisan commands if their dependencies are constructor-injected cleanly. Budget a day or two for that work and verify each command's service dependencies before committing to the port.
- Is speicher210/cloudinary-bundle safe and maintained enough for production?
- The technical risk is high based on adoption signals: one star, zero dependents, a single maintainer, and a bus factor of one. The release date of 2026-09-26 is future-dated, which is a metadata red flag you should confirm before procurement, and there is no field evidence of production use. MIT licensing is clean and the underlying Cloudinary PHP SDK is stable, but the bundle itself is a thin convenience shell. If the maintainer disappears, forking is realistic because the package is small.
- What Cloudinary PHP SDK version does speicher210/cloudinary-bundle pin, and could it block security patches?
- The provided context does not state the exact SDK constraint, so check the bundle's composer.json before adopting it. A pinned major version can block you from taking Cloudinary SDK security patches if the bundle is not updated promptly. Because the bundle is a thin wrapper, using the official Cloudinary PHP SDK directly gives you tighter control over upgrades and security fixes.
- How should I test a Laravel port of speicher210/cloudinary-bundle?
- Test the port at the boundaries: bind a fake or mocked Cloudinary client in the container, then assert that uploads, URL generation, and delete calls receive the expected parameters. Keep most tests off the live Cloudinary API and reserve a small integration suite for credential and transformation checks. Also test your Blade components directly, since replacing the Twig extension is where most regressions will appear.
- What are the best alternatives to speicher210/cloudinary-bundle for Laravel?
- The cleanest alternative is the official Cloudinary PHP SDK with a small Laravel service provider and Blade components you control. You can also look for Laravel-specific Cloudinary packages, or fork this bundle and take only the configuration schema, client factory logic, and console command bodies. If you need long-term maintenance, prefer the SDK-first route over depending on a one-star Symfony bundle.
Weaver
How can I help you explore Laravel packages today?