What's the correct upgrade path? Maple to Olive

Hi all
I’m currently running Tutor 13.1.0 which if I remember right was Maple, been a while since I installed this. I’m planning to upgrade to latest but want to confirm first the correct procedure? is it acceptable to just:
a) PIP install latest release, or
b) must one go iteratively through each of the 40-something releases since 13.1.0, or
c) should we do major versions only such as 13.1 to 13.2 to 13.3 to 14.0, etc…
thank you in advance

I’ve noticed an issue when running the tutor local upgrade\launch commands

docker compose -f /home/tutor/.local/share/tutor/env/local/docker-compose.yml -f /home/tutor/.local/share/tutor/env/local/docker-compose.prod.yml --project-name tutor_local stop
unknown shorthand flag: 'f' in -f

docker compose should actually be docker-compose
where do I find the upgrade\launch scripts that define this so I can manually adjust it?

I think I managed to solve my problem with the docker-compose issue

under /home/tutor/venv/lib64/python3.11/site-packages/tutor/utils.py
at line 196: def docker_compose(*command: str) → int:

Had to change:

    return execute("docker", "compose", *command)


    return execute("docker-compose", *command)
1 Like

@joel.edwards please follow this official document.


Thanks @Yagnesh
I have been following that, but it hasn’t been without it’s share of headaches.
The first command: pip install --upgrade “tutor[full]” fails due to requiring tutor-licence which is not compatible with tutor==13.1.0 as I have currently installed, even trying to upgrade to 13.1.1 is giving me errors with elasticsearch that I’m trying to troubleshoot now, as well as all my courses showing Page not found

I was able eventually to upgrade iteratively through the major releases one by one and get onto latest build with all my courses intact.

on most of the new versions I found that it kept reverting the docker-compose command to the wrong value, so I had to keep modifying the /site-packages/tutor/utils.py file as per my first reply, not sure if this might be a bug in those releases.