Weave Code
Storage Bundle Laravel Package
integrated/storage-bundle
A Symfony storage bundle that provides a simple abstraction for managing files, uploads, and storage paths across local and remote adapters, with configurable services and minimal setup for existing PHP applications.
Integrated Storage Bundle
Frequently asked questions about Storage Bundle
- Is integrated/storage-bundle a Laravel package?
- No. It is packaged as a Symfony bundle, with a Bundle class, a DependencyInjection extension, Configuration.php, and registration via config/bundles.php. Those conventions do not boot inside Laravel's service container without a bridge that your team would have to write and maintain. Even if the underlying code is framework-agnostic PHP, treat it as a Symfony dependency, not a Laravel package.
- How do I install integrated/storage-bundle with Composer?
- It is Bitbucket-hosted and will not resolve from Packagist, so you need a repositories VCS entry in composer.json plus CI credentials such as an app password or SSH deploy key. There are no published tags, so pin an explicit commit hash rather than a version constraint. Mirror the repository internally so a force-push or deletion upstream cannot break your builds.
- Does it replace Laravel's Storage facade and Flysystem?
- No, and that is the core evaluation problem. Illuminate\Support\Facades\Storage on top of league/flysystem already gives you disk configuration, local/S3/GCS drivers, temporary URLs, and streaming. The bundle's advertised value proposition of an adapter-based unified filesystem API overlaps with what Laravel ships out of the box. The burden of proof is on the package to name a concrete capability Laravel lacks, such as multi-tenant disk routing or resumable chunked uploads.
- Which Laravel versions and Flysystem major versions does it support?
- Unknown from the available metadata: there is no README surface, release history, or published dependency information to check. Laravel 9 and later moved to Flysystem 3, so a bundle written against Flysystem 1 or 2 will conflict at the dependency solver. Run composer why-not against your pinned laravel/framework and league/flysystem versions before spending any engineering hours.
- Can it handle large files and streamed transfers?
- The overview claims streamed reads and writes plus large-file support, but there is no documentation or test evidence to confirm it. Without reading the adapter source you cannot tell whether it genuinely streams or buffers entire objects into memory. Verify by inspecting the read and write paths and load-testing with files larger than your memory_limit.
- Is it safe for uploads, storage paths, and signed URLs?
- Storage code sits directly on classic attack surfaces: path traversal, content-type spoofing, and cross-tenant file leakage. A Bitbucket package with no public issue tracker, no tags, and no visible maintainer gives you no field evidence of how those cases are handled. Audit path construction, filename sanitization, and URL signing policy before letting it touch production uploads.
- Who maintains it and what is the release cadence?
- There is no visible upstream owner, tagging cadence, issue tracker, or release history, and the repository shows zero stars and zero dependents. That profile is consistent with an internal artifact or an early stub rather than a validated library. Confirm ownership with the Bitbucket project and ask directly whether it runs in any production application.
- What is the license and can we fork or redistribute it?
- The license is not documented in the material provided, so confirm the license file and redistribution terms with the owner before adoption. If forking is not permitted, you inherit a dependency you cannot patch or maintain if upstream goes quiet. Ask for read access, fork rights, and ideally a support agreement as part of procurement.
- What is the best alternative for file storage in Laravel?
- Laravel's native Storage facade backed by league/flysystem covers local, S3, and GCS disks with streaming and temporary URLs under first-party support. If you need extra behavior such as multi-tenant disk routing, virus-scan hooks, or retention rules, write a thin custom driver instead of importing a Symfony bundle. That keeps you on supported, auditable code with a known security response process.
- How should we integrate it if we decide to use it anyway?
- Never let application code call the package directly. Define an internal StorageGateway interface in your domain layer and implement it with an adapter that delegates to this bundle, so a swap is a single-file change. Pilot it on one non-critical bucket and gate adoption on a composer why-not check plus a proven CI authentication path to Bitbucket.
Weaver
How can I help you explore Laravel packages today?