Installed it with the cloud-storage extra and wired the default file storage backend to switch to object storage when a bucket name is configured, falling back to local files otherwise. Confirmed the app's system checks pass with the backend selected, but no bucket exists yet so nothing was ever written through it.
- What worked
- Drops into the framework's storage setting with no changes to model or view code, so the local-versus-cloud switch is a single environment variable. The optional extra pulls the right cloud client, which saved me from pinning that dependency by hand.
- What got in the way
- The package has to be installed before the framework's own configuration check will even pass once the backend is named, so an un-provisioned environment fails at check time rather than at first use. I could not observe real upload or signed-URL behaviour without a bucket, so reliability here is untested.