foreword

Since Google Chrome 63 will forcibly convert the domain name of *.dev to https, the domain name of the new version of D-Laravel will be changed to *.test.
This article explains how to update.

manual update

1. You need to manually remove the *.dev domain name in /etc/hosts in your computer, and you need root authority to modify /etc/hosts on the system.
You can also leave it alone, but some old *.dev domain names will remain in /etc/hosts.
You can modify it through vim, for example: sudo vi /etc/hosts to modify.

If you are a user of D-Laravel, when the entire computer only has the docker environment of D-Laravel , you can simply execute
./dlaravel uninstall
This will help you, remove all docker images, contianers and all *.dev settings on /etc/hosts.
Note, your computer has its own contianer of other projects, please do not execute this command.

2. After completion, you can execute git pull update in the Project folder of D-Laravel.
You may need to remove some configuration files generated under dlaravel/etc. It is recommended to directly install a new folder for testing.

3. Execute ./dlaravel to rebuild the domain name of *.test, according to the name of laravel projects in your dlaravel/sites folder.
 

new test install

If you are using an old version of D-Laravel, it is strongly recommended to clone a new one to test to see if it works normally.
For example the new folder is called dlaravelnew .
1.

git clone https://github.com/DevinY/dlaravel.git dlaravelnew

2. Copy the old version of data and sites/* (Laravel Project) to the new version of D-Laravel directory (dlaravelnew).
dlaravelnew/data (that is, Mysql data)
dlaravelnew/sites/ (the place where Laravel Project is placed)
3. Use normal as a template to copy out the docker-compose configuration file of the custom version.
cp docker-compose-normal.yml docker-compose-custom.yml
4. Force softlink to link docker-compose-custom.yml to docker-compose.yml
ln -vsf docker-compose-custom.yml docker-compose.yml
5. Please adjust and confirm whether the php version number and database version number used in docker-compose.yml in your old version of D-Laravel are the same as those in the new version.
If the difference between the old and new versions of the DB is too large, your db container may fail to open.
6. Execute ./dlaravel to recreate the domain name according to the name of the project folder in the sites.
7. ./console restart to test.
8. Under normal circumstances, you can use ./console info to check the domain names of all your projects: