I want this to function fully offline, and currently the image restrictions on Discogs CDN do not allow me to.
This overhaul PR adds a .NET API and Worker service that will listen to an input of IDs, and queue them up for processing, and the worker will gradually churn through ones that we don't have.
Not an ideal solution (can't wait so I expect the 2nd load of data will preserve) but eventually it will catch up and subsequent reloads won't take too long.
Arised as a strong complexity of #3.
I want this to function fully offline, and currently the image restrictions on Discogs CDN do not allow me to.
This overhaul PR adds a .NET API and Worker service that will listen to an input of IDs, and queue them up for processing, and the worker will gradually churn through ones that we don't have.
Not an ideal solution (can't wait so I expect the 2nd load of data will preserve) but eventually it will catch up and subsequent reloads won't take too long.