@foundeo what’s the startup time of minibox?

depends highly on the hardware / network — network to pull in the image (which is less than 100mb)

Do you have an article explaining what minibox is - how it compares to commandbox?

it is commandbox, but it is using box lite, which is using lucee lite

I do dev on neovim PDE for lots of other projects and for cfml I’d like to add some cfformat and cflint. But current commandbox startup is 8 seconds

yeah not sure if it will be faster, since I’m not sure waht neovim PDE is… if you are comparing pulling/running a commandbox docker image vs a minibox docker image, then minibox should be faster, but if you are comparing a

box.exe

vs docker run

docker run -it --rm foundeo/minibox:latest box

then I don’t think it will be much faster

I was thinking I'd start the container if not already started, then

docker exec container-name box fmt $[input_file}

anytime I want to. Feasible right?

@Daniel Mejia Minibox usually takes 5-10 seconds to run box depending on your hardware. As a general rule, running a binary inside of a docker container will always be slower than running the binary directly outside of docker!

yeah I found the path for the binary for box lite. I'm gonna try that next

Lite doesn't start up that much faster in my experience

ok

Now, what would be interesting would be to run a task daemon with a Rabbit RPC server in it which ran commands and "talk" to it via a Rabbit RPC client

so the daemon would start up one time and "talking" to it via the rpc client would be instant?

Yeah

the commandbox sytem tray tool talks to commandbox via what kind of client?

None

so how would the Rabbit RPC client talk to the box instance?

Magic 🙂