Closed jstockwin closed 8 years ago
I have the same issue, its a windows specific problem when the filename is resolved.
From node path
"The path.posix property provides access to POSIX specific implementations of the path methods."
Change line 92
return pathlib.posix.resolve(path, file.filename);
fixes it for me.
@cetchells Thanks for looking in to this! If you've already made that change, would you mind submitting a pull request to fix this?
I've just started trying to migrate an app to keystone v4.0.0-beta. I've currently got a working s3 setup. However, now I've changed to using
keystone-storage-adapter-s3
, the uploaded files on S3 have strange filenames, and these file names do not match what is stored in S3.The following is going to be a wall of code, but I figured I should provide all possible info.
My model is as follows:
I uploaded a file, which I called
testing
, however this is what it looks like on S3:Note that
D:\Documents\Development\GitHub\students4students\
is where my keystone app is stored locally, and not where the file is being uploaded from....However, on keystone, the file looks like this:
So when I try to get the file, which I do using
aws-sdk
, I'm essentially getting a 404 error. (The specified key does not exist).Sorry if it's me doing something wrong :)