Lucee Zero is a new smaller Lucee distribution without the admin or docs bundled.
This reduces the jar size by about 2mb and avoids expanding them on install, which makes Lucee initial startup a lot faster, as there is less to deploy.
Why an additional distribution?
Firstly backwards compat with existing build pipelines, as you can’t build a full install by adding just extensions, the admin simply isn’t there with Lucee Zero.
Secondly Lambas have some size limitations, you only have 50MB, when Lucee deploys, the .lco is extracted into lucee-server/patches and then the lucee-admin.lar and lucee-doc.lar are exracted out into lucee-server/context/context, plus inside the original lucee-zero.jar.
So this new distribution saves roughly 6MB of disk space, as there ends up being three copies of these two .lar archives on the filesystem once deployed.
When I run the local build for extensions, it’s about 6-7s faster (Lucee does deploy slower on windows than linux, so YMMV)
FYI: The Docs and Admin extensions you see in the admin, only add the required mappings to enable them, the admin is tightly tied to the release and is bundled in the core.lco file (by default)
Here are some examples of using the various Lucee distributions with Lucee script runner (default is 5.4.0.80)
Hi folks - I tried swapping this distribution into an existing Fuseless Lambda function but couldn’t get it to work; going to have a fiddle and see if I can get it going but the error on any URL is a “missing lucee-server/Component.cfc”. Any instinctive thoughts? Previously the function was using lucee-light-5.4.0.80 no problem. Thanks!
Hi @Zackster - so this is running on Lambda (Fuseless) without access to files, all I’ve done is a like-for-like between the release jars and the latest snapshots - both Zero and Light. I’ll send what I’ve got by email
to build their own home grown administrator “light”.