I mean, using Belt. 
jaimeiniesta
wmnnd
With Belt, you can’t currently upload data from memory but it’s an interesting idea. So for now I suggest writing the data to a file first and then using Belt.store/3.
How would you imagine the API for storing data to work? Should it take a stream (e.g. Belt.store_stream(config, stream, opts) or would you find it more convenient to store data directly (e. g. Belt.store_data(config, data, opts))?
2
NobbZ
Personally I think the following options would be nice to have:
- Upload from a file that exists physically on disc
- Upload memory content (a binary) literally
- Upload from a stream (chunked by size or by line)
- Upload from messages, in a way that the receiver can be passed in to HTTPotions
:stream_tooption.
2
wmnnd
I’ll think about how to implement this. For now, I recommend you create a temporary file and then specify the :key option in order to set the file name (file names are referred to as “keys” and directories as “scopes” in order to provide a more abstract concept that also applies to object storage).
0
jaimeiniesta
Cool, I got it working this way - the only thing now is that it’s super slow, a single file upload is taking like 10 seconds to upload to SFTP (but if I do that directly from my terminal, it’s fast). I’ll try to investigate about this tomorrow.
0
wmnnd
jaimeiniesta
wmnnd
Did you have the previous version installed? Maybe you have changed your mix.exs but not actually updated the version you have installed with mix deps.update? I also experienced very slow uploads with the previous version and 0.2.0 then introduced a different mechanism for SFTP uploads.
0
jaimeiniesta
No, I discovered Belt just today, it’s the first time I use it and it’s 0.2.0 - but I will investigate more tomorrow
0