-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Creating directories #14
Comments
Hi @frankdejonge , Is it possible to check the above issue and tell me if this is something that's gonna be integrated? Thanks in advance. Robbert |
@rvmourik I'm not sure about this one. With AWS there's a "supported" way, with rackspace it's not. Which would introduce a "flysystem flavoured" way of interacting with rackspace, making it less transparent. Is there a need for creating the directory? Are you creating a file manager of some sorts? |
Yes, it's going to be connected to a filemanager (elfinder for now). But if you can take a look here https://developer.rackspace.com/docs/cloud-files/v1/developer-guide/ and you search for "application/directory", you'll get to the informatie how directories are "supported". Isn't that their way of doing it and not a "flysystem flavoured" way like you suggested? |
@rvmourik ah I see. A PR is welcome then 👍 |
@frankdejonge Going to try that, never done that before :-) |
Hi,
We're using the adapter to use an object store as our filesystem, but creating directories was not working. After investigating we got to the conclusion the createDir method only returns a array with the dirname.
Altough Rackspace doesn't officially supports the use of folders, there is a way of getting this to work. In order for directories to work you need to send two additional headers with the request.
I've changed the createDir and normalizeObject to work with this solution.
createDir
normalizeObject
Is this something you'll be willing to integrate in the adapter, if so do you need a pull request (never done that before :-)) or can you manually use the above code adjustments.
The text was updated successfully, but these errors were encountered: