When we had our images on Wasabi, we had a the image checksum returned directly in the headers. This allowed us to validate the download.
Now that we are downloading from SCW, we don't have the checksum and thus download is not verified.
We could imagine the worker to upload the file checksum, store it in the UploadedFile and return that from the API. Probably good thing anyway.
Another demo-centered approach would be to download using the torrent and not the (first) HTTP source. We were not doing it because BT download using aria2c turns it into a daemon and we thus would have two process with one checking the status… it was a lot simpler to have a wget-like single process.
When we had our images on Wasabi, we had a the image checksum returned directly in the headers. This allowed us to validate the download.
Now that we are downloading from SCW, we don't have the checksum and thus download is not verified.
We could imagine the worker to upload the file checksum, store it in the
UploadedFileand return that from the API. Probably good thing anyway.Another demo-centered approach would be to download using the torrent and not the (first) HTTP source. We were not doing it because BT download using aria2c turns it into a daemon and we thus would have two process with one checking the status… it was a lot simpler to have a wget-like single process.