Weave Code
Storage Bundle Laravel Package
plusforta/storage-bundle
Plusforta Storage Bundle provides a flexible, configurable file storage layer for Symfony applications. It offers a clean service-based API for uploading, retrieving, organizing, and deleting files, with support for multiple storage backends and easy integration into existing PHP projects.
Symfony bundle for Flysystem integration
Frequently asked questions about Storage Bundle
- Is plusforta/storage-bundle a Laravel package?
- No. It is a Symfony bundle that wires Flysystem into the Symfony dependency injection container using a Bundle class, an Extension and Configuration tree, and compiler passes. Laravel uses service providers and its own container, so the bundle's registration model does not apply. Laravel applications should use the first-party Storage facade and config/filesystems.php disks instead.
- Can I install plusforta/storage-bundle in a Laravel app with Composer?
- You can pull the code down, but it will not register itself the way a Laravel package does, because Symfony bundles are enabled through bundles.php and the Symfony kernel. To make it work you would have to shim its services into a Laravel service provider, which effectively reimplements your existing filesystems configuration. There is no capability gap in Laravel that this package fills.
- What does this bundle give me that league/flysystem-bundle does not?
- From the public information available, nothing clearly differentiated. league/flysystem-bundle is the canonical Symfony integration, maintained by the League of Extraordinary Packages, with broad Flysystem and Symfony version coverage and real community adoption. This bundle appears to be a vendor-specific wrapper that may add internal adapter defaults or configuration conventions. If the only difference is defaults, that belongs in a config snippet, not a dependency.
- Which Flysystem major version does it target?
- This is unverified from the available information and is one of the key questions to close before adopting it. Flysystem 3.x changed adapter interfaces materially from 1.x, so a bundle pinned to an older major will not work with current drivers. Check the composer.json constraints for league/flysystem before committing to anything.
- What PHP and Symfony versions does it support?
- The version constraints are not documented in the public material reviewed, which is a red flag for planning purposes. A bundle published from an internal namespace often carries constraints tuned to one application, not to the wider ecosystem. Confirm the require and require-dev blocks on the actual repository before evaluating further.
- Is plusforta/storage-bundle safe to use in production?
- Treat it as high risk for anything that stores credentials or moves customer data. It has no visible adoption, zero dependents, and no issue traffic, which means no one has exercised it against current Flysystem or PHP versions in production. Installing an unadopted package from a non-canonical namespace is a genuine supply chain exposure. Prefer a package with a public commit history and an identifiable owner.
- Who maintains plusforta/storage-bundle and is it actively developed?
- It lives under a plusforta/public GitLab namespace with no stars, no dependents, and no community footprint, which reads as an internal package that was made public. There is no visible contributor base, SLA, or public commit history showing recent activity. If the vendor refactors internally, the public mirror can stall or disappear without notice. Silence in the issue tracker is not evidence of health.
- How do I test code that uses this bundle?
- Symfony bundles are typically tested by booting a kernel with the bundle enabled and overriding services in the test container, or by swapping the Flysystem adapter for an in-memory one. In Laravel you would not get Storage::fake() behaviour out of the box, since that helper is wired to Laravel's own filesystem manager. This is one more reason the bundle fits Symfony far better than Laravel.
- What is the best alternative for file storage in Laravel?
- Use the built-in filesystem layer: the Storage facade, disks defined in config/filesystems.php, and the S3, FTP, and SFTP drivers that ship with the framework. It is maintained by the Laravel team, documented, and tested with Storage::fake() for your test suite. Storage::disk() costs you nothing and avoids importing a foreign DI model into your application.
- Does this bundle support multiple storage backends and disk configuration?
- Yes, the overview describes a configurable storage layer that supports multiple backends through Flysystem adapters, exposing a service-based API for uploading, retrieving, organising, and deleting files. That said, the same flexibility is standard in both league/flysystem-bundle for Symfony and Laravel's own filesystem configuration. The feature set is not a differentiator; provenance and maintenance are the deciding factors.
Weaver
How can I help you explore Laravel packages today?