Is there a way to optionally not have filepicker.io store your uploads in their servers/database? -
maybe haven't read documentation thoroughly enough, seems if want use s3 option, it's typically because want serve uploads s3 location. once stuff in s3, doesn't need saved @ filepicker url anymore. there way specify want upload stored in s3, , not filepicker, making filepicker middle man?
one expect if possible, entail type of reduced cost due fact filepicker isn't storing data us. if possible, uploads stored in s3 , not filepicker still count towards our file limit account type have?
if specify s3 location, filepicker.io not store contents of file on our servers, why pricing plans done on # of files rather size, etc. on both filepicker.store()
, filepicker.pickandstore()
calls, fpfile returned have key
parameter indicates in s3 bucket file stored.
from this, can construct s3 url necessary, default provide filepicker.io url serves both unique identifier file, providing options /convert
, /stat
, etc.
Comments
Post a Comment