![]() ENV LUCEE_EXTENSIONS "16FF9B13-C595-4FA7-B87DED467B7E61A0?version=3.0.2.28"Ģ) Does the above “automatic upgrade” of the extension to a newer version after Lucee startup happen for a reason, for example is it because 3.0.2.29 is incompatible with Lucee 5.2.x. This raises a couple of questions, and possible feature enhancements ġ) Can we add support for installing specific versions of Lucee extensions via the LUCEE_EXTENSIONS environment variable (and system property), so that we can more easily produce repeatable builds if we need to? for e.g. I figured this might be a good workaround, however during the next startup of Lucee after the build (the build starts and stops Tomcat to “prewarm” the installation and ensure that Lucee starts up quickly), I see the following output in the console which shows that Lucee is downloading and installing version 3.0.2.29 of the extension rather than the 3.0.2.28 that I had previously downloaded fandango_1 | 1 15:35:13.538 INFO .Catalina.start Server startup in 2021 msįandango_1 | $AppClassLoaderįandango_1 | found memcached.extension-3.0.2.29.jar:falseįandango_1 | download memcached.extension:3.0.2.29 from and copy to /opt/lucee/server/lucee-server/bundles/memcached-extension-3-0-2-29.jar In our Dockerfile, instead of using the line with the environment variable, we can use wget to download the specific version of the Memcached extension and place it in the appropriate directory RUN wget -nv -O /opt/lucee/server/lucee-server/deploy/extension-memcached-3.0.2.28.lex There is another way to install Lucee extensions which is to drop them into the Lucee server deploy directory. ![]() However, let’s say that we need to install version 3.0.2.28 of the Memcached extension because we’ve found a bug in 3.0.2.29 that is causing a problem for us in production.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |