Lucee 6.2.1.122 Not saving setting and red 500 on restart

running all those tomcats is a lot of overhead, do what you want…

but please next time you do a bug report and you are doing something non standard, please clearly explain that from the outset, you really wasted a shit load of my time

I do really appreciate your bug reports, but please, paint a picture

Am I missing something? The way I learned to do Wars was to drop them in a Tomcat WebApps folder and use them. I am doing just that. How is this not a bug when version 6.2.0.321 Works normally, does not destroy itself and the other versions above that one do?

I have always been quite clear I am working with a War file.

Once again, I must be missing something with Lucee. How do you keep the secrets separate, and the websites of different users separate with their own settings when there is 1 .CFConfig file.

but you’re not just doing that, you’re copying around the WEB-INF?

I don’t ever use WAR myself, expect for supporting Lucee users, but my understanding with using a WAR is drop it in, let’s it deploy and don’t move around the WEB-INF like you described.

If you want proper client site isolation, these days the usual approach is to use docker

You can use the new secret manager

These days with single mode, it all about moving the config from json/xml, to Application.cfc

You are messing around with how Lucee does it’s standard deployment and then asking why it doesn’t work…

did you manage to make a repo?

Let me clarify this a bit more. I am deploying the war into a bind mount folder in the public_html folder of the website. Edit When you goto /opt/tomcat/webapps/example and ls the folder, you see WEB-INF, META-INF and the assests folder, and the website.cfm files and everything else. The tomcat hosts directive says

<Host name="example.com" appBase="webapps">
      <Context path="" docBase="/opt/tomcat/webapps/example/" />
      <Alias>www.example.com</Alias>
 </Host>

I do not know if I also made it clear that if I start with version 6.2.0.321
and drop in the lucee core file, the system updates and I have No Issues. It is only when I deploy a war file that this occurs, not anywhere else. Which is why I am asking what is so different in the WAR file compared to ALL the other ways of using Lucee.

Yes, as I left you a message in the issue tracker.