Weave Code
Object Store Laravel Package
ruwork/object-store
A lightweight object storage abstraction for Laravel and PHP applications. Store, retrieve, and manage objects through a clean, consistent API with pluggable storage backends. Integrates with Laravel's container and configuration, keeping persistence logic decoupled from your domain code.
At a glance
Frequently asked questions about Object Store
- What is ruwork/object-store used for?
- It is a thin object storage abstraction for Laravel and plain PHP applications, meant to sit between your domain code and a backend such as S3, Google Cloud Storage, or local disk. It offers a consistent API for storing, retrieving, and managing objects while keeping persistence logic decoupled from business logic. Architecturally the idea is sound, but it occupies the same slot as Laravel's native Storage facade and league/flysystem.
- Is ruwork/object-store still maintained?
- There is no evidence of active maintenance. The repository has zero stars, zero dependents, and no issue tracker activity, which is consistent with an abandoned or archived project. Zero upstream commits means your team owns every future compatibility fix if you adopt it.
- Does ruwork/object-store support Laravel 10, 11, or PHP 8.2 and 8.3?
- Almost certainly not officially. A package in this state was likely authored for PHP 7.x and a Laravel generation several majors behind current, and archived repositories carry no PHP 8.2/8.3 or Laravel 10/11 compatibility guarantees. Read composer.json to see the actual PHP and illuminate/support constraints before assuming anything.
- How do I install ruwork/object-store with Composer?
- It is Composer-installable and MIT-licensed, so composer require ruwork/object-store should work without legal barriers. Treat a successful require as the start of due diligence rather than the end: check the resolved PHP constraint, the Flysystem or AWS SDK version pulled in transitively, and whether the service provider registers correctly on your Laravel version.
- How is ruwork/object-store configured in a Laravel application?
- The package integrates with Laravel's container and configuration, but Ruwork packages often expose Symfony-style service providers that may need adaptation for Laravel auto-discovery. Verify how the provider registers, which config keys it expects, and which backend adapter it wires up before writing configuration of your own.
- Should I use ruwork/object-store or Laravel's built-in Storage facade?
- Laravel's Storage facade, backed by league/flysystem, already provides a mature, framework-supported abstraction over local disk, S3, and other adapters. Unless an audit shows ruwork/object-store adds something concrete, the native primitive is the lower-risk choice on any modern Laravel baseline.
- Does ruwork/object-store have tests, and can I run them today?
- Coverage is unknown and must be confirmed during a code audit; there is no community-tested integration to lean on. Run the existing suite against your target PHP and Laravel versions, and expect to write your own tests regardless. If you fork, add CI so the code is at least pinned by a green build.
- Is ruwork/object-store safe to use in production?
- Risk is high and asymmetric. The dominant failure mode is silent breakage on the next framework upgrade, discovered in production, with no upstream patch path for CVEs or PHP compatibility. It is defensible only inside a frozen legacy service you already own, and even then it should be wrapped behind an internal interface.
- How do I migrate from ruwork/object-store to Laravel Storage or Flysystem v3?
- There are two options: fork and own the vendor code, or replace it. Replacement is usually cheaper for a thin abstraction, so reimplement the small surface area against league/flysystem v3 and Laravel's filesystem manager, run both behind a feature flag, and cut over per environment with a rollback switch.
- How do I fork and maintain ruwork/object-store internally?
- Vendor the classes into app/Support, pin the commit, add tests and CI, and shim it behind an internal ObjectStore interface so vendor code never leaks into call sites. Record the build-versus-adopt decision in an ADR and assign an internal maintenance owner, including team, budget, and on-call, before you fork.
Weaver
How can I help you explore Laravel packages today?