I'm trying to upload a file using client.uploadFromStream by doing something like this:
if (exists(currPath) && isFile(currPath)) {
const fileStream = createReadStream(currPath)
.on('data', (chunk) => {
// logging for stream progress here
})
// Upload file from stream
await client.uploadFromStream(`${nextcloud_path}/${fileName}`, fileStream);
}
This does not throw an error and creates a file at the correct location on nextcloud, but the file is 0 Bytes/empty. If I write out the stream to a buffer, it correctly reads the data.
If i use client.put instead, everything works as expected, but then you lose the benefits of using the stream in the first place. Changing the example to the following works as expected and writes the actual content to the file on nextcloud.
I'm trying to upload a file using
client.uploadFromStream
by doing something like this:This does not throw an error and creates a file at the correct location on nextcloud, but the file is 0 Bytes/empty. If I write out the stream to a buffer, it correctly reads the data.
If i use
client.put
instead, everything works as expected, but then you lose the benefits of using the stream in the first place. Changing the example to the following works as expected and writes the actual content to the file on nextcloud.This leads me to believe that
uploadFromStream
is not working as I would expect it to.I have docker set up through TrueNAS, I don't think upload limits are the problem