Some subset of /app/public/media should be a shared volume on Akeneo

[andytson-inviqa]

On a project we need at least /app/public/media/cache to be a shared RWX volume so that nginx can serve cache of file resizes of uploaded images.

We're not sure if /media/ itself should be shared though

[a-ast]

Uploaded images and other files are stored in var/file_storage/ and those folder can be configured in
config/packages/{ENV}/oneup_flysystem.yml:

oneup_flysystem:
    adapters:
        asset_storage_adapter:
            local:
                directory: '%kernel.project_dir%/var/file_storage/asset'
        catalog_storage_adapter:
            local:
                directory: '%kernel.project_dir%/var/file_storage/catalog'
        jobs_storage_adapter:
            local:
                directory: '%kernel.project_dir%/var/file_storage/jobs'
        archivist_adapter:
            local:
                directory: '%kernel.project_dir%/var/file_storage/archive'
        data_quality_insights_shared_adapter:
            local:
                directory: '%kernel.project_dir%/var/file_storage/data_quality_insights_shared'

[andytson-inviqa]

this is the on demand image resize functionality I'm talking about. Seems nginx is supposed to serve it once generated.
var/file_storage is already a shared volume

[kierenevans]

I think this is when viewing those images in the browser. Presumably a web request to an akeneo container will resize images to public/media/cache if they don't exist there already.

In a highly available environment there will be multiple akeneo containers running, where the web request to akeneo will hit a different container from the second web request for a resized image.

[andytson-inviqa]

so my question is whether /media should be shared as well, or is /media/cache only what's suitable?