- What is AnzuSystems Core-DAM Bundle used for?
- It provides a reusable digital asset management foundation for PHP and Symfony applications. The bundle packages DAM domain models, asset and metadata abstractions, storage and persistence integration points, bulk operations, Elasticsearch-backed search, and media distribution workflows for images, videos, and podcasts. It is intended for teams building consistent asset management across AnzuSystems-style projects.
- How do I install AnzuSystems Core-DAM Bundle?
- Install it with Composer using anzusystems/core-dam-bundle, then enable the bundle in your Symfony application configuration. You will also need to configure the required dependencies and services, including Doctrine ORM, Messenger, Monolog, Elasticsearch, storage layers, and media-processing tools such as Vips or FFmpeg where applicable. Docker-based deployment is advisable because the media and search dependencies are operationally significant.
- Does this package work with Laravel?
- No, AnzuSystems Core-DAM Bundle is built as a Symfony bundle, not a native Laravel package. It requires Symfony 7.3+ and PHP 8.3+, so Laravel version support is not applicable without a custom bridge or adaptation layer. Laravel teams should evaluate Symfony-specific dependencies, service wiring, and event integration before attempting to reuse it.
- What are the system requirements for Core-DAM Bundle?
- The package requires PHP 8.3+, Symfony 7.3+, Doctrine ORM 3+, Symfony Messenger, and Monolog. Production deployments typically also need Elasticsearch for indexing and search, plus Vips or FFmpeg for media processing. MongoDB 2.0+ support is available via anzusystems/common-bundle, but may require a hybrid database setup if MongoDB is not already in your stack.
- Do I need Elasticsearch to use Core-DAM Bundle?
- Elasticsearch is a central architectural dependency for search, indexing, and metadata filtering. If Elasticsearch is unavailable or being reindexed, discovery workflows can be affected, so production use needs health checks, monitored reindexing, and fallback or cache strategies for critical search paths. Using the bundle without Elasticsearch would require significant adaptation.
- How does video import by URL work and what changed in version 1.53.1?
- Video import by URL depends on Symfony Messenger workers and media-processing infrastructure. Version 1.53.1 is a reliability fix in AssetFileChangeStateHandler that addresses a case where a worker killed during video processing could leave a 30-minute file lock, delaying video import by URL until expiry. Deploy 1.53.1, restart Messenger workers, and keep workers supervised and jobs idempotent.
- How should I test a Core-DAM Bundle integration before production?
- Test in Docker or staging with PHPUnit or Pest coverage, and validate Elasticsearch indexing, reindexing, and representative metadata search queries. Also test Messenger transports, Google PubSub credentials or fallback queueing, Vips and FFmpeg media processing, and worker crash scenarios for video imports. Sequence PHP and Symfony upgrades before bundle rollout to catch dependency regressions early.
- What monitoring and production safeguards are recommended?
- Monitor Elasticsearch health, reindexing progress, Messenger queue depth, PubSub delivery latency, and stuck or aging video-processing jobs. Supervise and automatically restart Messenger workers, make jobs idempotent, and scale workers horizontally during peak media uploads. Use circuit breakers or fallback search paths where appropriate, and document credential rotation for external services.
- Is MongoDB required for Core-DAM Bundle?
- MongoDB is not necessarily required for every deployment, but MongoDB 2.0+ support is available through anzusystems/common-bundle. If MongoDB is not already in your stack, introducing it can create a hybrid database setup that requires upfront schema design and query performance work. Benchmark early and follow the common-bundle guidance if you choose MongoDB-backed persistence.
- How actively maintained is Core-DAM Bundle and what alternatives should I consider?
- The package is maintained with patch releases such as 1.53.1, which fixes a video-import worker lock reliability issue, so teams should pin versions, review changelogs, and regression-test upgrades. Alternatives include a custom Symfony DAM implementation, managed DAM or CDN services, or Laravel-native media libraries if you are not committed to Symfony. Evaluate Elasticsearch operations, media-processing capacity, and long-term maintenance ownership before adopting it.