From c48822ec0c72ab32d88a567ee3d825b36a466e40 Mon Sep 17 00:00:00 2001 From: Zac Spitzer Date: Wed, 20 Sep 2023 11:54:56 +0200 Subject: [PATCH] add info for deploying on firewalled servers --- .../04.guides/12.deploying-lucee-server-apps/page.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/04.guides/12.deploying-lucee-server-apps/page.md b/docs/04.guides/12.deploying-lucee-server-apps/page.md index ab4443856..8019da554 100644 --- a/docs/04.guides/12.deploying-lucee-server-apps/page.md +++ b/docs/04.guides/12.deploying-lucee-server-apps/page.md @@ -34,6 +34,18 @@ The `/patches` folder is where Lucee's core `.lco` jars are kept. When Lucee st Extensions (`.lex`) can also be dropped in the `/lucee-server/context/extensions/available` folder and they can be installed using environment or JVM arguments without Lucee reaching out to the update provider. +## Firewalled Servers + +`.lco` updates either via the Lucee Admin update page, or by dropping into the `/deploy` folder, may require dynamically downloading any updated jar files from the update server. As such they may fail attempting to download the new files. + +To update firewalled servers, or to upgrade without Lucee downloading bundles (which is slightly slower), do the following + +1. Stop the server +2. Download the (fat) lucee.jar (see below) from [https://download.lucee.org/](https://download.lucee.org/) +3. Delete or change the file extension for the fat jar in the `lucee/lib` folder, i.e `5.4.3.2.jar` +4. Copy the updated `lucee.jar` into that `lucee\lib` folder +5. Start the server + ## Lucee Distributions available from [https://download.lucee.org/](https://download.lucee.org/)