For example, erec-yii2 copy becomes erec-yii2-upgrade.Įnsure you pull the latest vagrant updatesĪdd the following to the vagrant-local.yml file with your path to the new project if you already had a vagrant-local.yml. Therefore we need a seperate project for the upgrade branch since we still need to be able to work on v2.13.Ĭopy your current erec folder to the same location and rename it by appending -upgrade to it. The vendor folder does not change when you change branches. The installer will automatically add vagrant to your system path so that it is available in terminals. Vagrant is packaged as an operating-specific package.
#VAGRANT UPGRADE INSTALL#
Doing so allows us to have mysql 5.7 in the regular way and 8.0 in a container. To install Vagrant, first find the appropriate package for your system and download it. After consulting with Steve, we agreed that the best way to have a second version of mysql, is to use a docker container. Having two version of mysql is more difficult as the second version would upgrade the original version. Having two versions of php in linux is easy as each version installs in its own directory, allowing us to point to whichever version we want to use. One of them being the project itself being updated from Yii2 2.0.12 to 2.0.35. This is the only way we can have 2.13 and 2.14 since the vendor folder has a ton of differences between the two versions. To do this, we will be adding 2.14 as a seperate project. Also, since the vendor folder does not switch with the branch switching, we need to have different vendor folders for each version. In order to do this, we need our vagrant to have two versions of php, 7.1 and 7.4, and two version of mysql 5.7 and 8.0. We need to be able to have version 2.13 and 2.14 on the same vagrant in order to work on both versions of the project.
0 kommentar(er)
