We are ditching the excessively normalised data structure for files.
Now file variations are embedded in the original file document for
improved performance.
Keep file removal, but do not remove file when encoding video until
everything is encoded. Also limit the response from GCS Post. Using
blob_to_dict leads to threading issues (due to signed url generation).
Good fix if you want to get involved in Pillar development!
We introduce a new node_type, storage, which can support different file
storage backends and makes them available for browsing via dedicated
entry points in the application. We intend to keep pillar storage
agnostic and support both internal/local storages as well as
remote/hosted solutions.
Introducing the asset of type file creation. This involves making a
node collection entry of type asset, as well as a file collection
entry, plus all the needed variations if such file is an image or a
video. Further, depending on the storage backend (pillar or other) we
synchronise the files there using rsync. Currently this functionality
is available only via pillar-web, since a web interface is needed to
upload the file in a storage folder, which is shared between the two
applications.
