-
Notifications
You must be signed in to change notification settings - Fork 40
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
[FEATURE] Add "base folder" configuration setting #116
base: master
Are you sure you want to change the base?
Conversation
Hi @cweiske, |
Hey together, Given a have the following folders in the bucket and only wanna see
I would like to see it merged 👍 |
To be honest I still don't see a good use-case for the "base folder". Using a single S3 bucket for multiple use-cases does not look like a best practice architecture to me. For each use-case there should be a separate S3 bucket (e.g. don't mix private and public data in a single bucket). If you're using different folders to setup a permissions layer for a single use-case the TYPO3 built in feature of file mounts is exactly what you're looking for. |
I do not know why it has once been decided that some of the projects I'm working on are sharing the same S3 bucket. What I know is that permissions on the bucket level have all been correctly setup by the admins. As for "why base folder instead of file mount": |
The base folder allows us to use the same bucket for multiple projects by forcing every project/TYPO3 instance into an own prefix: ``` mybucket/ + project1/ | + file23.jpg | + subfolder/ | | + subfile42.png | + _processed_/ | + ... + project2/ + file2.jpg + _processed_/ + ... ``` The prefix is not visible in the TYPO3 UI (file list, file information) and gets added transparently to S3 requests, and is removed from S3 responses as well. My initial version used a simpler approach by just overriding `getRootLevelFolder()` and `getParentFolderIdentifierOfIdentifier()`, but this led to inconsistencies in the UI, and the processing folder could not be moved into the base folder because of inconsistencies inside the TYPO3 API.
The base folder feature needs functional tests, and thus is blocked by #153. |
The base folder allows us to use the same bucket for multiple projects by forcing every project/TYPO3 instance into an own prefix:
The prefix is not visible in the TYPO3 UI (file list, file information) and gets added transparently to S3 requests, and is removed from S3 responses as well.
My initial version used a simpler approach by just overriding getRootLevelFolder() and getParentFolderIdentifierOfIdentifier(), but this led to inconsistencies in the UI, and the processing folder could not be moved into the base folder because of inconsistencies inside the TYPO3 API.