Background
ObjectStorageManager is currently written with production object storage backends in mind, primarily s3 and minio. This works for deployed environments, but it makes local development and testing unnecessarily restrictive.
In local test scenarios, it is often more convenient to use the file storage scheme instead of requiring an S3-compatible backend.
Problem
The current logic in ObjectStorageManager treats s3 and minio as the primary supported schemes and does not cleanly support local file storage usage. This creates friction for:
- local integration testing
- debugging Retina object buffer behavior
- reproducing storage-related issues without external object storage dependencies
Background
ObjectStorageManager is currently written with production object storage backends in mind, primarily s3 and minio. This works for deployed environments, but it makes local development and testing unnecessarily restrictive.
In local test scenarios, it is often more convenient to use the file storage scheme instead of requiring an S3-compatible backend.
Problem
The current logic in ObjectStorageManager treats s3 and minio as the primary supported schemes and does not cleanly support local file storage usage. This creates friction for: