Aggregated Css & js assets are not uploaded to s3

Created on 16 July 2024, 4 months ago
Updated 17 July 2024, 4 months ago

Problem/Motivation

Aggregated Css & js assets are not uploaded to s3

Steps to reproduce

1. Enable s3fs Module & configured
2. Enable s3fs_assets module
3. Enable the css & js aggregation under performance tab
4. Aggregated css & js files are not created in Aws s3

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report
Status

Active

Version

1.0

Component

Code

Created by

🇮🇳India Asheef Chennai

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @Asheef
  • 🇦🇲Armenia 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.

Production build 0.71.5 2024