Weave Code
Code Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
File Distribution Bundle

File Distribution Bundle Laravel Package

aboutcoders/file-distribution-bundle

Symfony bundle providing database-backed file management and distribution. Define filesystems in config or persist via Doctrine ORM, then store and transfer files across local, FTP, or CDN targets. Built on the AbcFileDistribution library and unit tested.

View on GitHub
Deep Wiki
Context7

Symfony file distribution bundle

Frequently asked questions about File Distribution Bundle
Can I use AbcFileDistributionBundle directly in Laravel, or is it only for Symfony?
This bundle is designed for Symfony and isn’t natively compatible with Laravel due to its tight coupling with Symfony’s AppKernel, dependency injection, and Doctrine ORM. However, the underlying **AbcFileDistribution library** (if available separately) could be adapted for Laravel with custom abstraction work.
What Laravel alternatives exist for managing files across multiple storage backends (local, FTP, CDN)?
For Laravel, consider **Spatie’s Media Library** (local + CDN), **Cloudberry** (CDN management), or Laravel’s built-in **Filesystem** with **queued async transfers** for FTP/CDN sync. These are more lightweight and Laravel-native compared to this Symfony bundle.
How do I configure filesystem definitions in AbcFileDistributionBundle? Can I skip the database and use YAML/XML instead?
You can define filesystems either via **Doctrine ORM** (default) or directly in Symfony’s configuration (YAML/XML). The bundle supports **LOCAL, FTP, and CDN** types, with options like `path`, `host`, and `create` flags. Skip the database by setting `db_driver: false` in config, though this limits persistence.
Does AbcFileDistributionBundle support Eloquent models instead of Doctrine?
The bundle currently relies on **Doctrine ORM** (or MongoDB/Propel ODM), but its architecture suggests Eloquent could replace Doctrine entities with minimal effort. You’d need to adapt the bundle’s persistence layer or use a wrapper to abstract the ORM.
What Laravel versions and PHP versions does this bundle support?
This bundle is **Symfony-specific**, so Laravel version compatibility isn’t guaranteed. The underlying library likely supports **PHP 7.2+**, but direct Laravel integration would require additional work. Check the **AbcFileDistribution library’s docs** for PHP version requirements.
How do I test file transfers between FTP and CDN in this bundle?
The bundle includes **unit tests** for core functionality. For FTP/CDN transfers, mock the filesystem adapters in your tests (e.g., using Symfony’s `Filesystem` or Laravel’s `Storage` facades). Test edge cases like connection failures or permission issues explicitly.
Is AbcFileDistributionBundle production-ready? What’s its maintenance status?
The bundle has **low adoption (1 GitHub star)** and limited activity. Check the **last commit date** and **issue tracker** for responsiveness. For production, consider alternatives like **Spatie’s Media Library** or **Cloudberry**, which have broader community support and Laravel-specific optimizations.
Can I use this bundle for large-scale media libraries (e.g., user uploads) in Laravel?
While the bundle’s **file distribution logic** is valuable, its Symfony dependencies make it a poor fit for Laravel. Instead, use **Laravel’s Filesystem** with **queued jobs** for async CDN/FTP transfers, or leverage **Spatie’s Media Library** for a more integrated solution.
How do I migrate from Symfony’s AbcFileDistributionBundle to a Laravel-compatible solution?
Start by extracting the **core file transfer logic** from the bundle (e.g., FTP/CDN sync) and rewrite it as a **Laravel service** using Laravel’s `Storage` facades. Replace Doctrine entities with Eloquent models, and use Laravel’s **config system** instead of Symfony’s YAML/XML.
Are there performance concerns with database-backed filesystem definitions in this bundle?
Database-backed definitions add **latency** for file operations compared to Laravel’s native filesystem drivers. For high-performance needs, consider **caching filesystem configs in memory** or using **Laravel’s cached filesystem adapters** instead of a full ORM layer.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
codifyo/ts-generator-bundle
andydefer/laravel-cluster
testo/fiber
mintobit/jobqueue
a4sex/maintenance-bundle
a4sex/entity-date-update
a4sex/client-identifier
a4sex/base-utilites
a4sex/key-value-storage
a4sex/micro-status
chilldev/dependency-injection-extra
datinglibre/datinglibre-app-api
biberltd/corebundle
bricre/symfony-bundle-test
biberltd/logbundle
dominium/http-adapter-bundle
dominium/google-analytics
a4sex/auto-clean-entity
christhompsontldr/laravel-inky
spatie/mailcoach-vapor