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
Prevent ContentType assignation when dirs are created. #164
Conversation
Holla! Could you update the tests for this too? Also, just a quick question, why do you create directories on s3? |
Hi, We create directories via this adapter because s3fs' performance is very bad and in order to prevent CPU problems in the other system. |
Do you actually need the directories? Because s3 itself doesn't need them. What's your use-case? |
Yes, because we deploy the same core in different environments with different adapters (Local, S3, etc...) and we need to ensure that the directories exist for the following processes, otherwise, we have to be constantly checking this and as I said, s3fs has performance issues. |
Hi @frankdejonge , Any chance to keep an eye on the changes I've suggested?. Thanks! |
Dude, the PR is 19 hours old. |
Oh, sorry. Yesterday we were having a conversation and I thought it would be more fluid. Many thanks. |
Also, I want to first check what the consequences are for DO spaces and AWS S3 itself before merging to see if it doesn't cause regressions. I'm also moving house now so I expect to get to this somewhere next week at the earliest. |
Ok, no problem. Many thanks, and apologies. |
This is released as 1.0.23 |
Amazing, thanks a lot!. |
Thank you for your contribution 👍 |
ContentType assignation is not needed for directories and this cause unexpected behavior in third-parties like s3fs.
Using this adapter, if you create a directory and you try to read it via s3fs you get an error because it is managed as a file.
Sample code,
Accessing via s3fs (in other system outside PHP environment),