I just finally switched the lucee docs build from ...
# lucee
z
I just finally switched the lucee docs build from
commandbox
over to lucee/script-runner Now the docs build takes 2mins instead of 4mins https://luceeserver.atlassian.net/browse/LD-160
👍 1
1
b
If you use a Docker image like
foundeo/minibox
as your base runner, you don't need to spend any time installing CommandBox 🙂
e
docker images are security risks, besides 50 percent gain in performance is awesome!
b
@Evil Ware Every CI server I know of already uses docker images to run your build so you're not getting away from using a docker image. The suggestion was simply to use a docker image that already has box installed. Secondly, Zac reported the slow down was in actually taking the time to install box every run. Using a docker image with box already present removes that. So my suggestion would also bring about the same increase in performance.
z
I'm quite happy with 9s, just 57s to fire up lucee and render out all the docs
e
@bdw429s We could ask zac, to me it seems that maybe providing the Jenkins code to automate this could be in order so that lucee can be built by anyone with the want to play around with automated containers. I am not ranting about commandbox, it's a great framework engine, but if you can tweak an item to less than half the time, it's awesome. As for your observation about commandbox and containers, the reason anyone should build their own container is obvious. from a security standpoint. Then again, I only program as I like eating and hot showers. ....https://www.bleepingcomputer.com/news/security/docker-hub-repositories-hide-over-1-650-malicious-containers/
b
Lucee doesn't use Jenkins. It uses Github actions and the builds are already all publicly available.
I have no idea what your link to an article about malicious code that people happened to put into a Docker container has to do with the idea that Docker is somehow inherently insecure 🤔
e
RTFA
Docker itself, like any item, is secure when it's configured right and you know where it came from. The problem is the vast majority of "IT Professionals" will happily run a binary, as it was found as a free download. Rolling your own code from the source is best, but if you do not even understand the mechanics behind it, then you could be a target for malicious characters.
b
I'm addressing this blanket statement you started the thread off with however
docker images are security risks
which was in reply to me suggesting he use an image created by Pete Freitag-- the foremost security expert in the CFML space.