The good part: I have pushed the TUS Go application to heroku and its sitting their waiting for work to do.
The confusing part: when I click to upload a file with Uppy, it sends out a request to an http address instead of the https address I have it configured with.
I am putting together a reverse proxy on heroku to allow the https calls to be passed on to the TUS server but I am confused why the request doesn’t go out with the https protocol specified.
Thanks @marius that helped, not sure how I missed that…
By default the tusd server writes to the server file store. Where would I find those? I don’t see them.
Also, should I be using tus in conjunction with the @uppy/aws-s3 plugin? I am currently using the @uppy/aws-s3 plugin and it’s working great…just trying to see how tus plays its part.
If I have an application that allows user to upload files using uppy, say the user starts to upload huge file…they start uploading but then refresh the page. What would I need to do to get the file uploading again? Just trying to understand how the different parts of your awesome offering work together.
Ryan, I am having the exact same problem, I think that I have followed the guidance referenced above by Marius, but it’s not working for me yet. Could you please share exactly what you needed to do to solve the problem?
Thanks, Jeff