- Issue created by @Asheef
- 🇷🇸Serbia lebster
I have tested this module and noticed that specified bucket root (root folder) is not always good option. For example, if you need to store something out of public access on the same bucket, like private files etc. So, I made a minimal version that really takes the most logic from s3fs and Drupal system with a minimal changes.
Another thing related to fact that assets:// scheme does not managed by s3fs module, so the second patch s3fs-assets-support-3461756-2.patch is recommended to make it work.
I can't be 100% sure that everything work well, I'm in active testing process at moment.
- 🇬🇧United Kingdom pasive
Does not work at all.
Even after applying both patches and following instructions on README.
Site attempts to load assets from local file system and not S3. - 🇳🇿New Zealand berenddeboer
All working for me on Drupal 11. Obviously had to patch this module to allow me to enable it with Drupal 11, but otherwise no changes.
So there are cases where this module simply works. However it wants to write to the s3 bucket root /js and /css prefixes. Not great, but not a problem.