Weave Code
Storage Bundle Laravel Package
swp/storage-bundle
swp/storage-bundle is a Symfony bundle that wires a configurable storage layer into your application, giving you one abstraction for reading, writing, and managing files across local and remote backends. Service-based configuration keeps storage concerns out of your application code.
[READ-ONLY] Subtree split of the Superdesk Web Publisher Storage Bundle
Frequently asked questions about Storage Bundle
- Is swp/storage-bundle a Laravel package or a Symfony bundle?
- swp/storage-bundle is a read-only subtree split from Superdesk Web Publisher and is packaged as a Symfony bundle. The overview describes a lightweight storage abstraction, but the technical evaluation found no Laravel service provider, facade, or config publishing. Treat it as a Symfony/SWP component, not a Laravel-native dependency.
- Can I install swp/storage-bundle in a Laravel application with Composer?
- Direct Composer installation in a modern Laravel app is likely to create dependency conflicts with PHP 8.x, Symfony components, Doctrine, or Laravel packages. The bundle has no visible releases since 2018 and is a read-only subtree split. Run an isolated compatibility spike before adding it to your Laravel composer.json, and prefer Laravel-native storage if that spike fails.
- Which Laravel and PHP versions does swp/storage-bundle support?
- The available context does not document supported Laravel versions, and the last release was in 2018. Modern Laravel on PHP 8.x is unlikely to be compatible without patching. Verify PHP, Symfony component, and Doctrine constraints in an isolated container before planning any integration.
- How do I configure local disks or S3-compatible storage with swp/storage-bundle?
- Configuration is service-based in the Symfony bundle, not Laravel config publishing. The overview mentions disk profiles and per-environment overrides, but Laravel developers should not expect config/storage.php publishing or a Storage facade. For Laravel, map the required disk profile to Laravel's built-in filesystem disks or a maintained Flysystem adapter instead.
- Does swp/storage-bundle integrate with Laravel's Storage facade or Flysystem?
- Do not expect Laravel Storage facade integration from this package; the evaluation found no Laravel-native abstractions. It may wrap Flysystem concepts in Symfony services, but you would need custom adapters for Laravel. Laravel's built-in filesystem layer already provides Flysystem-based local and S3-compatible disks.
- Is swp/storage-bundle actively maintained and safe for production?
- Maintenance risk is high: the package is a read-only subtree split, last released in 2018, with zero stars and zero dependents in the assessment. There is no Laravel community support or package-specific issue tracker in the split repository. Production use would make your team responsible for patching, security review, and dependency updates.
- What license does swp/storage-bundle use and what are the AGPL implications?
- The assessment identifies AGPL-3.0 licensing, which requires legal review for network-accessible services. AGPL obligations can affect how you deploy modified versions, including SaaS use. Get legal approval before adopting it or forking it.
- How does swp/storage-bundle handle multi-tenant prefix scoping and path normalization?
- The overview advertises path normalization and safe prefix scoping for multi-tenant setups, but those claims come from the package description rather than a Laravel integration test. In Laravel, you can achieve similar isolation with per-tenant filesystem disks and explicit path prefixes. Validate any scoping behavior in an isolated spike before relying on it.
- What are the best alternatives to swp/storage-bundle for Laravel storage abstraction?
- Use Laravel's built-in Storage facade and Filesystem/Flysystem integration for local and S3-compatible disks. For custom backends, choose maintained Flysystem adapters or a small internal adapter behind a Laravel-native interface. This avoids Symfony bundle conventions and AGPL licensing concerns.
- How should I evaluate or migrate from swp/storage-bundle without disrupting my Laravel app?
- Do not plan a drop-in migration: isolate the storage concepts you need, prototype a Laravel adapter or sidecar service, and validate data migration and rollback. Run the package only in an isolated Symfony container first, not in the Laravel app. If the spike fails, stop early and implement the behavior with Laravel Filesystem/Flysystem.
Weaver
How can I help you explore Laravel packages today?