Weave Code
Objectstorage Laravel Package
linkorb/objectstorage
Linkorb ObjectStorage is a lightweight PHP abstraction layer for object storage, providing a consistent API to upload, retrieve, and manage files across local and cloud-backed storage systems. It simplifies integrating multiple storage backends into PHP applications.
linkorb/objectstorage provides a unified PHP interface for working with object storage backends, letting you read, write, and manage files across providers without rewriting integration code. It abstracts away provider-specific APIs behind a consistent, storage-agnostic layer.
- Pluggable storage adapters for multiple backends
- Simple read/write/delete operations on objects
- Stream-friendly handling for large files
- Framework-agnostic, PSR-compatible design
Frequently asked questions about Objectstorage
- Is linkorb/objectstorage still maintained and safe to use in a Laravel app?
- No. The last release was 2019-08-09, the repository is unknown so there is no source review, CI signal, or security response path, and no upstream fixes have shipped in over six years. Treat it as unmaintained legacy and only keep it where existing code already depends on it, ideally behind an internal interface.
- How do I install linkorb/objectstorage with Composer?
- Install it with composer require linkorb/objectstorage, but run composer require --dry-run in a throwaway branch against your real constraint set first. Its 2019-era pins on Guzzle, Symfony, and PSR packages may conflict with Laravel 10/11 and aws-sdk-php. Pin the exact version in the lockfile and never allow a VCS branch.
- Does linkorb/objectstorage support Laravel 10 and Laravel 11?
- There is no confirmed support. The package predates PHP 8.1/8.2 and Laravel 10/11, and its implicit nullable parameters, dynamic properties, and deprecations are unverified. Because the repository is unknown, Laravel package discovery, service providers, and PSR-4 autoloading cannot be confirmed without a spike.
- Which storage backends does linkorb/objectstorage connect to?
- The description mentions Amazon S3, local disk, and others, but the exact adapter list (GCS, Azure, Swift/OpenStack) is not verifiable from the available metadata. Confirm the specific adapters you need before relying on it. Fit is only plausible for a provider genuinely not covered by Flysystem.
- How does linkorb/objectstorage compare to Laravel's Storage facade and Flysystem?
- Laravel's Storage facade, backed by league/flysystem v3, already ships first-party S3, SFTP, FTP, and local adapters plus presigned URLs, streaming, and per-disk configuration. Adding linkorb alongside it creates a second parallel abstraction with duplicate credential resolution, two error models, and test doubles that Storage::fake will not cover. For greenfield work, use Flysystem.
- Does linkorb/objectstorage support streaming, multipart uploads, and presigned URLs?
- These capabilities are unverified, since the metadata does not show them and the repository is unknown. Assume they are missing until a spike proves otherwise. If you need them in Laravel today, the Flysystem S3 adapter is the safer choice.
- How do I wrap linkorb/objectstorage so I can replace it later?
- Define an internal ObjectStore contract covering only the operations you actually use, such as put, get, delete, exists, url, and stream. Implement two adapters, one backed by Flysystem and one by linkorb/objectstorage, then run a conformance suite covering CRUD, large objects, unicode keys, missing keys, and auth expiry against both on a real bucket. Cut over disk by disk via a configuration flag and keep the legacy adapter as a fallback for one release.
- What is the migration path off linkorb/objectstorage?
- Inventory every call site and classify it by operation, then define an internal interface that covers them. Build a Flysystem-backed adapter as the default, run a conformance suite against both implementations, flip over via a configuration flag, and remove the dependency once traffic is fully migrated. Budget one to two engineer-days for the initial spike to confirm installability and the public API surface.
- What dependency conflicts should I expect from linkorb/objectstorage?
- Its 2019-era releases pin older Guzzle, Symfony, and PSR packages, which will likely clash with Laravel 10/11 on PHP 8.1/8.2 and with aws-sdk-php. Composer may force downgrades elsewhere in the application. Run composer require --dry-run first; a Guzzle or Symfony conflict is an immediate stop signal.
- What are the best alternatives to linkorb/objectstorage in Laravel?
- Use the built-in Storage facade with league/flysystem-aws-s3-v3 for S3, plus the first-party local, SFTP, and FTP adapters. If you need a provider Flysystem does not cover, write a custom Flysystem adapter instead of adopting a second abstraction. Both options give you active maintenance, PHP 8 support, and a working security response path.
Weaver
How can I help you explore Laravel packages today?