Upgrading Version

When upgrading CheckCle, it’s important to note that the process is not limited to pulling the latest Docker image. A full upgrade also involves updating the database schema to match the new version requirements. This ensures that all new features, bug fixes, and structural changes are properly applied and the system continues running smoothly.

The upgrade process generally includes:

1. Removing and Pulling the latest Docker image – to get the newest application code and improvements.

# Find and stop the existing container
docker ps -q --filter "name=checkcle" | xargs -r docker stop

# Remove the stopped container
docker ps -a -q --filter "name=checkcle" | xargs -r docker rm

# Remove the existing Docker image
docker images -q "operacle/checkcle" | xargs -r docker rmi

# Pull the latest CheckCle image
docker pull operacle/checkcle:latest

# Start a new container with the latest image
Run the container from the existing Compose file with:
docker compose up -d

# Alternatively, you can run it using the docker run command.
docker run -d \
  --name checkcle \
  --restart unless-stopped \
  -p 8090:8090 \
  -v /opt/pb_data:/mnt/pb_data \ # make sure you put the correct existing path
  --ulimit nofile=4096:8192 \
  operacle/checkcle:latest

# Verify the container is running and logs
docker ps | grep checkcle
docker logs -f checkcle

1. Applying database schema migrations – to update tables, fields, or relationships required by the new version.

   • Go to the About System page in the dashboard.

   • You will see a new Update Schema button — simply click it to update, as shown in the image I shared with you.

1. Verifying compatibility – checking that the upgraded application and database are aligned, with no missing fields or mismatched structures. and also check the version number in the about system page.

2. Testing the system after upgrade – confirming that alerts, monitoring, and integrations continue to work as expected.