Weave Code
Laravel Flysystem Cloudinary Laravel Package
codebar-ag/laravel-flysystem-cloudinary
Flysystem adapter that plugs Cloudinary into Laravel's filesystem, letting you store, retrieve, and manage uploaded images and files through the familiar Storage facade. Simple configuration and seamless integration with Laravel's native upload, URL generation, and file handling APIs.
Cloudinary Flysystem integration with Laravel.
Frequently asked questions about Laravel Flysystem Cloudinary
- How do I install codebar-ag/laravel-flysystem-cloudinary?
- Install with composer require codebar-ag/laravel-flysystem-cloudinary, publish the package configuration, and add a Cloudinary disk entry in config/filesystems.php. Set your cloud name, API key, and API secret through environment variables rather than committing them. A working spike should take under a day; the real effort is validating the Flysystem operations your app depends on.
- Which Laravel and PHP versions does this Cloudinary Flysystem package support?
- The package targets Laravel applications on PHP 8.1+ with Flysystem 3, but the exact Laravel 10, 11, and 12 support matrix is not clearly documented in the overview. Check the composer.json constraints and CI configuration in the repository before adopting it. Run your own smoke test on the Laravel version you deploy.
- How do I configure a Cloudinary disk in Laravel's filesystems config?
- Add a disk in config/filesystems.php using the package's Cloudinary driver and reference credentials from your .env file. Publish the package config if it provides one, then confirm the disk name you use with Storage::disk('cloudinary'). Keep this as a dedicated media disk alongside your existing local or S3 disks rather than replacing them.
- Does it support Laravel Storage facade methods like put, get, and url?
- The adapter is strongest for put() uploads and url() delivery, which covers the common media upload and serving flow. Flysystem operations such as readStream, listContents, setVisibility, and move or copy may be partially supported or behave differently because Cloudinary is not a POSIX-like filesystem. Build a written matrix for the operations your app uses and test each one before relying on them.
- Can I generate Cloudinary transformation URLs through the adapter?
- Transformation support through url() is not confirmed in the provided overview, so do not assume the adapter builds transformation URLs for you. Many teams generate Cloudinary delivery URLs with transformation segments outside the adapter or in a small helper. Verify the adapter's url() output and keep transformation logic under your control.
- Does it support private assets and signed Cloudinary URLs?
- Cloudinary delivery is public by default, and private assets require authenticated delivery or signed URLs. The overview does not make clear whether this adapter exposes those features cleanly through Laravel's Storage API. Complete a security review and test signed URL generation before storing any non-public content.
- Can I use this package for general-purpose file storage like documents or backups?
- Cloudinary is best treated as a media pipeline rather than a general-purpose object store. Flysystem assumes path-based semantics, deterministic listing, and read-back streams, and those assumptions leak on Cloudinary for archival storage, private documents, and byte-for-byte retrieval. Keep local or S3 disks for documents, backups, and anything requiring strict filesystem behavior.
- Is codebar-ag/laravel-flysystem-cloudinary actively maintained and production ready?
- Adoption signals are weak: the package has around 12 stars and a single-agency maintainer, so battle-testing and community redundancy are limited. The MIT license lets you fork and vendor the adapter if maintenance stops, but budget for that contingency. Check recent commits, release history, and maintainer responsiveness before committing.
- How should I test Cloudinary uploads in a Laravel application?
- Laravel's Storage::fake() may not exercise the real Cloudinary adapter behavior, so it is not sufficient for validating uploads and URL generation. Write integration tests against a Cloudinary test account or mock the HTTP layer, and cover only the operations your application actually uses. Include failure cases such as 429 and 5xx responses if your app depends on them.
- What are the alternatives to this Laravel Cloudinary Flysystem adapter?
- If you need a full object store, use S3 or local storage with Laravel's first-party drivers instead. If you want Cloudinary-specific features, the official Cloudinary SDK or a small custom Flysystem adapter may give you more control. Wrapping storage behind your own interface reduces the cost of replacing this adapter later.
Weaver
How can I help you explore Laravel packages today?