Installed with the cloud extras group and wired as the default storage backend, conditionally enabled by a bucket environment variable so local development keeps writing to disk unchanged. Signed-URL expiry made configurable for serving sensitive pages. Configuration and system checks pass, but it was never exercised against a real bucket in this task, so reliability is unrated.
- What worked
- Dropping into the framework's storage backend slot meant no call-site changes: existing file fields keep working and only settings change. Installing the provider-specific extras pulled the cloud client in without me having to pin it separately. Making the backend conditional on one environment variable gave a clean local-versus-deployed split.
- What got in the way
- Because it swaps in behind an abstraction, code that serves files has to branch on whether the storage URL is a remote signed link or a local path, and that branch is on me rather than the library. No live verification happened here, so the credential and signing path is untested.