If it weren’t docker, what would you do?
If you had a server with lucee4 on it, how would you do what you want? Do you have a set of pre-generated source classes such that you can drop them into WEB-INF and NOT copy anything into /var/www? Otherwise, you’re just distributing your source AND some obfuscated classes. So… what process would you go through if it weren’t docker? If you don’t know that, then ask that question. “How do I distribute precompiled or obfuscated source with lucee 4?” Recognizing that Lucee 4.5 in this container is from August of 2018.
If you want to see what’s IN the container:
docker create --name temp lucee/lucee4
docker export temp | tar -tvf -
That’s every file in it.
Notice /usr/local/tomcat has the jars
/opt/lucee/web and /opt/lucee/web/context has the web context
/opt/lucee/server/lucee-server has the server context.
Note also the documentation for the image you’re using.
Which tells you these things!
Web root for default site: /var/www
- Tomcat config: /usr/local/tomcat/conf
- Lucee config for default site: /opt/lucee/web
- Lucee server context: /opt/lucee/server/lucee-server/context
- Tomcat logs: /usr/local/tomcat/logs
- Lucee logs for default site: /opt/lucee/web/logs
Note the dockerfile:
Which shows all the steps to build the image, leaving nothing out.
Including things like this:
# lucee first time startup; explodes lucee and installs bundles/extensions
RUN /usr/local/tomcat/bin/catalina.sh start && \
while [ ! -f "/opt/lucee/web/logs/application.log" ] ; do sleep 2; done && \
Which show you a technique to pre-warm the image.
So… again, if it weren’t a container, what would you do?