ToVersionparameter. If the container is online, it will try to get the update package from the
updatepackagesvolume first. If not found, the container will download it from the
workflowgen-releasesGitHub repository. If the container is offline, it will try to get the update package from the
updatepackagesvolume. If it can't, it will write an error message and exit.
updatepackagesvolume, the container expects the following file structure:
update.zip, which is the WorkflowGen official update package. You need only to have the
ToVersionupdate package when you run the container.
WFGEN_UPGRADE_UPDATE_PACKAGE_FILE_NAMEenvironment variable. For example, you could specify the value
7.15.2and the directory structure is flat. You could also specify the value
workflowgen/updates/7.15.2/update.zipif the update package is further down the directory tree.
App_Datafiles into existing
Wsfolders are ignored, including during the merge operation. The container will then merge the
App_Datafiles from the update package into your
App_Datafolder that you have linked to the container through the data bind mount. The merge is additive only, which means that any file that don't exist in the update package will be kept as-is.
wfappsfiles into existing
App_Datamerge operation, the
wfappsfolder will also be merged with your
wfappsprovided in the data bind mount. This operation is also additive only.
/mnt/data/wfappsrespectively and apply any database migrations using the SQL scripts in the update package.
ToVersionargument passed to the container. You would call the container like this:
-Offlineflag has been passed to the container. This flag tells the container to not try to download the update package if it doesn't find the package in the bind mount. In other words, the container will not attempt any network-related access.