Store analysis queue using storage drivers #123
Etiquetas
Sem marco
Sem responsável
1 participante(s)
Notificações
Data limite
Data limite não informada.
Dependências
Nenhuma dependência definida.
Referência: aheathershaw/blue-twilight#123
Carregando…
Referência em uma nova issue
Nenhuma descrição fornecida.
Excluir branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Following the implementation of #121, it’s only possible to separate the bulk processing work to another server if a shared file system is in use due to the temporary analysis queue being hard-coded to write to the file-system.
We should provide a config option to choose what storage backend (driver) should store the analysis queue, allowing it to be stored on cloud storage, and thus easily shared between servers.
This will be required for BT Cloud.
The new config option should live in the new Image Processing tab introduced in #121 and default to the file-system.
New interface methods will need to be introduced (or a complete new interface?)
This needs implementing for “replace image” and bulk uploads.