You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's my understanding that this should upload directly to the Shrine cache store (at Rails.root + tmp/shrine). However, it seems to be initially storing the file in /tmp, and then copying it over once the upload is complete, but before Shrine can respond back to the browser. This means I get a bit delay once the upload hits 100%.
Anyone got any clues on why it's still writing temporary RackUploadedFile* into /tmp ?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In my app, I've mounted an upload endpoint to work with Uppy, and I've pointed it at the cache store:
It's my understanding that this should upload directly to the Shrine cache store (at Rails.root + tmp/shrine). However, it seems to be initially storing the file in /tmp, and then copying it over once the upload is complete, but before Shrine can respond back to the browser. This means I get a bit delay once the upload hits 100%.
Anyone got any clues on why it's still writing temporary RackUploadedFile* into /tmp ?
Beta Was this translation helpful? Give feedback.
All reactions