Weave Code
Storage Bundle Laravel Package
unite-cms/storage-bundle
A Laravel storage bundle for Unite CMS that provides a flexible layer for managing files and media within your CMS. It integrates storage configuration and file handling into the Unite CMS ecosystem, helping you organize and serve uploaded assets in PHP applications.
Unite CMS Storage Bundle adds a flexible, pluggable storage abstraction layer to Unite CMS. It decouples your content and media from any single filesystem or database, so the same application code can persist data locally, in cloud buckets, or via custom drivers—configured through simple, environment-aware settings.
- Pluggable storage adapters for local filesystems and cloud services
- Unified API for reading, writing, moving, and deleting content objects
- Per-field and per-content-type storage configuration
- Framework-friendly dependency injection and service wiring
- Extensible driver interface for building custom backends
Frequently asked questions about Storage Bundle
- Is unite-cms/storage-bundle compatible with Laravel?
- No. It is a Symfony bundle built for Unite CMS, and it relies on Symfony's service container, form types, and Twig views rather than Laravel's service providers, facades, Blade, or filesystem abstraction. There is no Laravel package discovery metadata, and integration would require a compatibility layer or a rewrite. Treat it as a Symfony/Unite CMS package, not a Laravel package.
- Can I install unite-cms/storage-bundle in Laravel 10 or 11?
- It is very unlikely to install cleanly. The last release was in 2018, so its Composer constraints probably target PHP 7.x and Symfony 3 or 4, which conflict with modern Laravel requirements. Run composer require unite-cms/storage-bundle in an isolated Laravel 10 or 11 app and inspect composer why-not to confirm the exact blockers. Expect to need dependency overrides even if installation is forced.
- What does unite-cms/storage-bundle actually do?
- It adds storage abstractions, fields, and views for managing files and images in S3 within Unite CMS content types. It provides configurable storage adapters and integrates with the CMS core to handle uploads, assets, and stored files. Its value is specific to the Unite CMS and Symfony ecosystem, not general Laravel file management.
- Does unite-cms/storage-bundle provide S3 uploads for Laravel applications?
- Not natively. The package is designed around Symfony and Unite CMS form types, Twig views, and service configuration, so it does not expose Laravel-ready S3 upload fields or Blade components. You can inspect its S3 upload and validation logic as a reference, but you should implement uploads with Laravel's Storage facade or a maintained package. Do not assume its AWS SDK integration is current.
- What PHP and Symfony versions does unite-cms/storage-bundle require?
- The exact constraints are not stated in the provided overview, but the 2018 last release strongly suggests PHP 7.x and Symfony 3 or 4 era dependencies. That likely conflicts with PHP 8+ and current Laravel versions. Check the repository's composer.json and run composer why-not before making any integration decision.
- Is unite-cms/storage-bundle actively maintained?
- No. It has not been released since 2018, has very low community validation, and shows no dependents in the assessment. That means no active maintainers, sparse documentation, and no ongoing security or dependency updates. Your team would own all patches and upgrades if you adopted it.
- What are the production risks of using unite-cms/storage-bundle?
- The main risks are outdated AWS SDK dependencies, possible S3 signature or API breakage, and unpatched security issues after years without updates. The upload implementation may also lack chunked uploads, retries, CDN integration, or efficient image handling, so throughput and reliability are unverified. Lack of tests and community usage increases uncertainty in production.
- What are good Laravel alternatives for S3 file and image management?
- Use Laravel's native Storage facade with the s3 disk for uploads and URL generation, and add validation and image processing as needed. For richer content fields, evaluate maintained packages such as Spatie Media Library, Filament file upload fields, Tall fields, or Laravel Nova file fields if you use Nova. These options fit Laravel's service container, Blade, and filesystem abstraction without a Symfony compatibility layer.
- Can I reuse the S3 upload logic from unite-cms/storage-bundle in Laravel?
- You can review it as a reference for field behavior, validation, and S3 adapter patterns, but direct reuse is risky because it is tied to Symfony services and likely old AWS SDK versions. Extract only framework-agnostic ideas, then rebuild the upload flow with Laravel Storage, validation rules, and a modern front-end component. A clean Laravel-native implementation is usually cheaper than forking and modernizing the bundle.
- How should I migrate from unite-cms/storage-bundle to a Laravel-native solution?
- Timebox a short spike to confirm Composer incompatibility and review the bundle's S3 field and upload logic. Then prototype a Laravel-native file or image field using Storage::disk('s3'), Laravel validation, and Blade or a component such as Livewire or Filament. Compare rebuild effort against forking; given the package's age and low maturity, rebuild is the safer default. Also evaluate maintained alternatives before committing to custom code.
Weaver
How can I help you explore Laravel packages today?