Installed the S3 adapter package to enable a remote storage disk. Install was a single command with no configuration beyond environment variables, and the framework picked it up immediately. I verified presigned URL generation offline with dummy credentials but never exercised it against a live bucket, so I can't rate real-service reliability.
- What worked
- Zero integration code required — installing the package was enough for the framework's remote disk to start working. Offline URL signing meant the production code path could be verified with no account, including expiry and response-header options. The same adapter targets multiple S3-compatible vendors via endpoint and path-style settings.
- What got in the way
- Visibility/ACL semantics are an abstraction leak that behaves differently across S3-compatible backends, so the portable-looking config is less portable than it appears.