Hello, what is the recommended upgrade method for Lucee? I just did an upgrade in place within the admin, which then required me to restart Lucee in order for the Applications tab to work. After upgrading, although I see 6.2.0.321 in the header of the admin, I see 6.1.1.118 for the loader version in the system info and Tomcat 9.0.8. Is it better and/or recommended to upgrade using an updated installer instead?

Ideally you need to automate your deployment, both for dev and production, docker is a good approach. There's a bit of a learning curve, but you'll be enjoying the ease for ever after.

Thank you @zackster!

The in place upgrade doesn't change the loader, you can just stop, drop the lucee.jar in the lib folder and restart to update the loader. How did you install?

I clicked on upgrade inside the server admin

I meant originally, via the installer?

Via windows installer

Yeah, I'd do a fresh install, you can do a side by side stall with the new installer

At the moment, I am going to just uninstall, then install the new version and import my config

Perfect

Thank you @zackster, at least now I know it was not me doing something wrong 🙂

Pro tip, it's always a good idea to take a copy of your cfconfig.json

That is what I did 🙂

You can just drop it in the deploy folder after you install

ok cool, thanks!

Just wait up to 60s, no need to restart

Thank you!

Honesty it better to send at an app level, but for quick n dirty, the extension works ok

Yes I use it on my applications already

Inbox zero 💪

@zackster while I have your attention. I did notice that it now installs in single mode but it appears that it gives me issues when I am using it with multiple applications and I have to change it to multi-mode. My quick example is based on running 2 coldbox apps and while browsing both, it would appear that the settings would collide ( if that makes sense ). So which ever started first, is what appeared to be the main app. Each application has its own name and they are both different sites on IIS. Once I switched to multi-mode, this issue would not occur. This was on 6.1. Is that expected in single vs multi mode?

So application one would sometimes get the config from application two on different hostnames?

yes

In single mode it's only separated by what ever the application name is

I would assume each site would be treated as different applications

Not in single mode, there's only one namespace

Ok cool, thank you for confirming that

Did the file disappear from the directory? Anything in deploy.log?

Should I use the old

.CFConfig.json

that was in the context folder vs my cfconfig export I did?

The context one is safer, it's 100% compat, cfconfig should be as well, but there are edge cases

ok let me try that now

Glad I could help 🎉

Hey jc, like zackster hinted, I too recommend migrating your apps to docker containers. Doing so will make upgrading and deploying much easier.

This client does not use docker, but I agree as well.

do you still have a stacktrace for the admin applications page error? https://luceeserver.atlassian.net/browse/LDEV-5359

Hello @zackster, I do not as I did a full re-install