We’re trying to get around this issue - https://dev.lucee.org/t/lucee-forcing-v2-0-1-25-of-the-s3-extension/14608. Basically, on Lucee v5, you can’t seem to install a different version of an extension if it has a version of that extensions that gets bundled in the core. We’ve tried the LUCEE_EXTENSIONS environment variable and copying and pasting the .lex file to the deploy folder, but it gets installed, then the core version gets installed over it instead. We tried Lucee v6 where this bug is fixed, but some of the box products aren’t ready for Lucee 6. Can anyone think of how to install a specific version of an extension when it is also bundled in the core of Lucee? I can share Dockerfiles if that would be helpful.

Use Lucee light so there isn't anything bundled with the core and then specify only the extensions you want in

LUCEE_EXTENSIONS

That’s a good idea. I went down that path before trying to go to Lucee 6 but moved on before I vetted it all the way. Lucee 6 installs extensions it needs when it goes to use them whereas Lucee 5 you have to install the stuff the core is expecting, otherwise it fails. So maybe we just work through those. Hmm. Good option to explore.

We also found it easier to drop the Lucee S3 extension and just use the Ortus library. No reason S3 should be part of the app engine

The latest s3 extension makes things pretty easy (if we can get it installed 😄 ). I’m not familiar with the Ortus library. Do you mind sharing a link?

if you are looking at other libraries, i use aws-cfml and its been good. i haven't looked at S3 SDK so can't compare, but it can be good to have options ... https://github.com/jcberquist/aws-cfml

I've used both, John's stuff is always good

Those are both great options as well. Thanks a ton for the suggestions!

i should look into those, because: • https://luceeserver.atlassian.net/browse/LDEV-4100 • https://luceeserver.atlassian.net/browse/LDEV-2630