Our Vagrant boxes are expected to be used for development, so we make them track our QA branches (i.e. the development branches). However, after a release is completed, the qa branch is renamed to stable, so the next major release becomes the QA branch - for example, now we've prepared the upcoming 2.5.4 release in stable/2.5.x, but are putting the latest feature development into qa/2.6.x.
Note: if you have test data in your vagrant box that you wish to keep, make a backup first, and then load the sqldump back in before running the upgrade task (a step covered in the slides linked below). We'll be running the purge task at one point, which will purge all your data!
Originally, this box was tracking the development branch (qa/2.5.x) but that branch has been deleted. You can easily update your vagrant box, however: First, check out the stable/2.5.x branch:
- cd atom
- git checkout stable/2.5.x
- git pull --rebase
From here, you can follow slides 19 and onwards in the following deck:
The one difference might be the command to restart PHP-FPM - I can't recall if we have PHP 7.0 or 7.2 in that particular vagrant box (you can try running php -v to check). If the version is PHP 7.2, then you would restart PHP-FPM with the following:
- sudo systemctl restart php7.2-fpm
You may also want to double-check the atom-worker configuration file, located at /usr/lib/systemd/system/atom-worker.service, to see if it conforms with the changes we introduced in 2.5 to make the job scheduler more stable - see:
If you make any changes, be sure to run the rest of the maintenance commands listed on that page.