Implemented inside the backstage area, see #26. Uploaded images are stored directly in the correct location (see below), and an entry in the processing collection is created:
Implemented in #46. Watches processing collection for entries with state = new, fetches uploaded images, extracts meta data and converts images to the correct sizes, then uploads all of that.
Media storage
Currently, media is stored right inside the folder for a given entry. Each variant has a prefix:
Purpose
This issue serves as a concept for an architecture which enables us to process uploaded media online. Key requirements:
Overview and flow
User uploads
Implemented inside the backstage area, see #26. Uploaded images are stored directly in the correct location (see below), and an entry in the processing collection is created:
Media processor
Implemented in #46. Watches processing collection for entries with
state = new
, fetches uploaded images, extracts meta data and converts images to the correct sizes, then uploads all of that.Media storage
Currently, media is stored right inside the folder for a given entry. Each variant has a prefix:
The original uploads will be stored alongside these without any prefix, e.g.
20221113_151718315_iOS.jpg
.