Use with Drupal 10.1

I missed that the D10.1 beta went out last week.

Moving to active.

No other major API changes have been seen in 10.1 and our original blocker has been tested as resolved.

Will give it a quick manual with takeover usage check (since our functional tests are a bit lacking in that regard) and report back.

So if I understand the one assets ticket that’s now configured separately? And what’s the benefit again for now being on s3

So if I understand the one assets ticket that’s now configured separately?

Correct, core now in D10.1 uses a new streamWrapper with a configurable local path instead of public:// to store CSS/JS assets. This new system is no longer 'lifetime sensitive" with relationship to the nodes that generate them and can self-generate at any time in the future.

And what’s the benefit again for now being on s3

I believe its still the same argument as before, just without css/js assets being stored, which in fairness aggregates have had some performance impacts, especially when paired with ADVAGG, as bucket access time for Drupal to read/write them can take some time.

The shortlist of some reasons to use s3fs are:

• Allowing an environment to operate with multiple front-end servers, shared filesystems are still mandatory, the new css/js assets:// stream is only for css/js assets and does not solve general file storage.
• Allow storing files larger than local disk space available, or larger than a host file size limits may allow (Pantheon 100mb upload limit when used with s3fs_cors)
• Possible reduction in operating costs, depending upon provider, S3 storage can be cheaper (compared to Amazon EFS) and less complex to manage than local storage.
• Possible increase in performance on the Drupal frontend (IOPS and network transfer related to serving static assets are transferred to a different server)
• Simplification of backups and Disaster Recovery

I'm sure more reasons can be created for individual sites, that is just the short list of what I can see of the top of my head.

Note: this hasn't been tested with ADVAGG yet as they do not currently have 10.1 support, see 📌 Document which parts of the module are still relevant after aggregation changes in 10.1.0 Needs review .

@smustgrave in addition to what @cmlara listed, there are platforms where it's completely necessary to store uploaded files on a separate file system, such as on DigitalOcean's App Platform, which functions more like a CI/CD process in that every deploy completely wipes the file system and installs everything from scratch.

Merged into dev with a minor text only change to the README after original review.

I have one other issue I want to try and slip in before we tag a release. I will aim to be able to have a tagged 8.x-3.3 before the end of next week unless a new disruptive bug emerges.

Automatically closed - issue fixed for 2 weeks with no activity.