Hi , just got back from camp and catching up on this. I see the zip files in Github. Do we just need to place these on S3 and update ForgeBox?

The update workbench repo can be found at https://github.com/jclausen/commandbox-cfengines (initial commit is still pushing up and it's large commit so give it an hour or so from 11:15 AM CST). The zip files for the engines are in the /adobe directory.

ACF11 gave me a ton of trouble and required that I apply each hotfix in sequence. Attempting to upgrade more than 1 version at a time broke Commandbox's ability to start the war. As such, each incremental version is included with the distribution ZIP files.

The workflow for upgrading any of the engines is:

1. Download the latest hotfix
2. Build and start the docker Tomcat container for the engine

docker-compose build cfengine-acf(major version)
docker-compose up cfengine-acf(major version)

3. run docker ps to find the process id of the server then copy your hotfix in to the docker/ACF(major version)/WEB-INF/cfusion/hf-updates directory

4. Open up a bash shell inside the docker container:

docker exec -i -t (process ID from above) /bin/bash

5. Run the hotfix manually:

java -jar /usr/local/tomcat/webapps/Engine/WEB-INF/cfusion/hf-updates/(hotfix jar)

6. Stop the container with CTRL+C, CD in to the /Engine directory and create the WARfile: jar -cvf Engine.war *

7. Move the generated WARfile up to the parent directory, remove or rename the docker-generated `Engine` directory and start with Commandbox: server start cfengine-acf(major version)

8. Pull the new version ID from the settings summary page, update the box.json file and zip.