With Robodog, you’d typically upload to Transloadit’s ingestion network, and then Transloadit performs some converstion, and uploads both the original and mutations to its final destination (if s3, via multipart yes).
If you’d want to upload directly to aws s3, you could make Transloadit then import the files and do something with it, but this requires more boilerplate on your part as it’s not among the primary use cases that Robodog was built for. It would probably be better to not use Robodog then, but use the lower-level Transloadit Plugin to string things together.
Initially the use of Transloadit is not so much for processing but leveraging the global network to speed uploads (if I’m correct that’s one of the benefits in addition to the processing?)
Multipart is needed because we’re dealing with large files of up to 2 gb, and a whole job could be up to 14gb. I’m still getting my head around all the options and configurations as to which is the best combination of solutions, while I test out the flows & WordPress integration options.
According to https://uppy.io/docs/transloadit/ Tus is already included so we don’t actually need to do anything there?
ie: “As of Uppy version 0.24, the Transloadit plugin includes the Tus plugin to handle the uploading, so you no longer have to add it manually”