Help me understand the manual update process

I am trying to script Lucee updates, using PowerShell, so I don’t have to manually log into the Lucee admin in all my servers and update them.

Do these steps sound correct? I am running Lucee 5.x on Windows.

1. Stop the Lucee service
2. Remove any old jar files from C:\lucee\lib (I found that if I left the old ones in there, the new one would not be applied when I restart Lucee)
3. Copy the new jar file into C:\lucee\lib
4. Start the Lucee service

This seems to work, the only downside is I cannot roll back to a previous version through the admin interface. I would like that ability.

It seems that if I:

1. Stop the Lucee service again
2. Copy the previously removed jar files back into C:\lucee\lib
3. Start the Lucee service

Now I have the previous versions in the drop down in the update page in the Lucee admin. I have not scripted this last part (copying the old jar files back into c:\lucee\lib) because I’m afraid if I stop the Lucee service in my script, immediately after the start service command completes, that the update will not be finished being deployed.

Thoughts? Thanks.

4 posts - 2 participants

Read full topic