what side effects should i be aware of if i were t...
# lucee
j
what side effects should i be aware of if i were to consider moving from the regular lucee docker image to the light version?
-light
(optional) is a build with the Lucee "Light" JAR file, WITHOUT any extensions (users must install extensions separately, this includes database drivers, ORM, ESAPI, S3, image handling, etc)
i figure there would be some extensions that i may need to install manually. however, i wonder if there would also be a side effect of a given lucee version not having a default, pinned, version of any given extention.
s
We've always used lucee light. It just means we have to specify all the extensions we want in our Dockerfile
👍 1
Lucee light still 'works' so it doesn't depend on any of those extensions, but there are some your code may take for granted
j
i'm already installing some optional extensions (and some newer versions of certain extensions) in the fat image but there's a certain behavior that i can rely on there for built-in extensions: a given version of lucee will have a given default, pinned version of a given (LAS) extension. perks of that: • i don't have to explicitly pin extension versions for "stock" extensions • without explicitly pinning extension versions, i still get the newer (but still implicitly pinned) versions of stock extensions. (IOW, i upgrade stock extensions when, and only when, i upgrade lucee, which can be a good thing)
in the light version are there default/implicit extension versions for a given version of lucee or will i need to start pinning all extension versions if i don't want them upgrading unpredictably?
s
In lucee light there are no extensions at all, as far as I know
The whole point is to divorce the engine from the extensions
I think but don't like relying on this behavior that it will try and fetch an extension if your code asks for it, and it will grab the latest production release
so we always pin everything
I'd check on that behavior though, don't take my word for it
j
okay, i think that last bit answers my question, since you're pinning everything. i'll do an experiment with an older and newer light version and see which version of, say "compress tags" i get with a really old lucee light image and the latest light image.
i figure it's as we both both expect: that we'll get the latest extension version, regardless of which version of lucee it is.
s
I'd expect you wouldn't get compress at all unless your code invokes it
at which point lucee will stop, go fetch it, install it, and then yes, it should be the latest production release regardless of what version of Lucee you're running