one valuable use case: development copies of a public website (eg WikiRate)
- live site needs write access to live bucket. we could, in theory, turn off delete access to reduce risk of accidental data loss.
- dev site needs configuration for read access to live bucket so that the site can use images from the live site
- typically speaking, we probably want to have a separate dev bucket, so that when we test things on dev, we're not adding nonsense to the live bucket.
- same general pattern applies to demo, staging...
- however, we may eventually also want a solution for dev that lets us commit files/images to the live site if/when we know we want them to be available. (not needed right away)
another valuable use case: Heroku deployments should work with this configuration!