Weave Code
Object Store Bundle Laravel Package
ruwork/object-store-bundle
Symfony bundle that wires a configurable object store into your app. Register storage services, persist and retrieve objects through a clean API, and keep storage concerns decoupled from domain logic. Suitable for files or serialized data with simple configuration.
At a glance
Frequently asked questions about Object Store Bundle
- Can I install ruwork/object-store-bundle in a Laravel application with Composer?
- No. It is a Symfony bundle built around Symfony's Bundle class, DependencyInjection extensions, and configuration tree processing, which do not map onto Laravel's container or provider lifecycle. A composer require will not wire it up, so integrating it is a port rather than an install. Treat it as a reference implementation instead.
- Is ruwork/object-store-bundle still maintained?
- No, the repository is archived, so there are no security patches, PHP or Symfony compatibility updates, or issue triage. Adopting it transfers permanent ownership to your team. It also has effectively zero stars and dependents, so there is no community validation or reported production usage. Plan for a fork or replacement.
- What does ruwork/object-store-bundle actually do?
- It is a Symfony bundle that wires a configurable object store into an application and registers storage services through Symfony's dependency injection container. It exposes put and get style operations so storage concerns stay decoupled from domain logic. It is intended for files or serialized data with simple configuration, but the documentation gives no guarantees on supported backends or credential handling.
- Does it wrap Flysystem or implement its own storage transport?
- The available evaluation does not confirm this, and it is the first thing to verify in a code review. If it delegates to Flysystem or a cloud SDK, the package is replaceable in an afternoon. If it implements its own transport, signing, or retry logic, that is the only part worth preserving. Check the service classes and composer.json requires before deciding.
- Which Laravel versions does ruwork/object-store-bundle support?
- None, because it is not a Laravel package at all, so there is no Laravel version support to speak of. It targets Symfony, and its archived status means its Symfony and PHP constraints may conflict with a modern lockfile. Do not plan for direct integration in Laravel. Use Laravel's filesystem abstraction or Flysystem directly instead.
- How do I configure the object store in this bundle?
- Configuration goes through a Symfony configuration tree processed by a DependencyInjection extension, not Laravel's config publishing. You would define storage services and parameters in Symfony configuration and let the bundle register them. There is no equivalent path in Laravel without rewriting the extension as a service provider. Documentation on backends and credentials is not guaranteed.
- What are the PHP and Symfony version constraints for ruwork/object-store-bundle?
- They are not listed in the provided context, and archived bundles typically pin older Symfony and PHP versions. Run a Composer dry-run against your current lockfile before any deeper work. Changes to the symfony/config and symfony/dependency-injection APIs are the usual breakage points for older bundles. If constraints conflict, you can block unrelated upgrades.
- How should I migrate from ruwork/object-store-bundle to a Laravel-native solution?
- Define a first-party ObjectStore interface with put, get, delete, exists, and presigned-URL methods, then implement it with Flysystem or a cloud SDK adapter. Your application should never import the bundle's classes, so swapping or dropping the package becomes a one-file change. Mirror any richer contract semantics into your port selectively. This inverts the dependency and removes the abandoned code from your graph.
- Is ruwork/object-store-bundle safe to use in production?
- It is high risk because it is archived and has zero stars or dependents, meaning nobody has reported production failure modes. There is no security patching and no documentation guarantees on credential sourcing, multipart uploads, retries, or stream handling. If you adopt it, you own it permanently. Most teams are better off using a maintained Flysystem adapter.
- What are the best alternatives to ruwork/object-store-bundle for Laravel?
- Laravel's built-in filesystem abstraction, league/flysystem, and the official cloud SDKs cover the same object-store use case with active maintenance. For Symfony, use a maintained Flysystem bundle instead. If you like this bundle's interface shape, copy the contract rather than the package. That gives you the decoupling benefit without the archived dependency.
Weaver
How can I help you explore Laravel packages today?