I’m in the process of migrating a Lucee installation from the older multi-context mode to the single-context mode introduced in Lucee 6. We run many sites on the same Lucee server instance, and all sites share the same folder structure, including common folders like /functions, /components, and so on.
The issue I’m facing is that, while in multi-context mode each site had its own isolated component namespace and classloader—meaning, for example, functions.tokens in Site A would only load Site A’s /functions/tokens.cfc and the same for Site B—now with single-context mode, components from Site B are being loaded in Site A. This is causing conflicts.
How can I prevent one site from loading another site’s components in this single-context setup?
I’d really appreciate any insights or advice you can share!
Okay — the reason I made the post is that I thought it was something I had to work around when using single context, since I’ve never used it before. ChatGPT gave me the impression that this behavior was somehow unavoidable (strange as that sounds ). But thankfully, it turned out to just be a bug
I’m also on Lucee 6.2.1.122 Apache Tomcat 11.0.6 on Windows in production.
We’ve been migrating our code from BlueDragon.NET 9 after New Atlanta closed to Lucee 6. Appreciate all the work from the Lucee community on developing this Open Source product.
I can certainly upgrade our test servers to run 6.2.2 RC while I test out running multiple sites on a single-mode server. Production doesn’t need that for now but will at some point.
Which leads me to my question. Is there a guide, post, something that describes the best strategy for configuring a multiple site setup with configuration settings in application.cfc on a single-mode server.
We’d like to stay current with Lucee (which is v6 now and v7 soon) but also have multiple sites that need site specific configuration settings with a single server setup.
I did see the following articles:
I didn’t know if there was another other discussion of this anywhere else (i.e. blog posts, articles, whatever).
Also, second question (possibly a dumb one), is there an LLM Lucee recommends using (over others) for devops/operations type questions regarding Lucee? I can’t imagine there would be, but seeing your comment about checking preplexity I thought I would ask.
I use perplexity myself, it’s really good at picking up all the latest posts here and on Lucee docs and citing links back to the source articles.
If there’s things missing from the documentation or you have further questions, feel free to ask questions here and we can update those docs with relevant information, those answers usually show up in perplexity the next day.
). But thankfully, it turned out to just be a bug