But anyways, with the secure copy commands I supplied, you are better safe than sorry! I am not sure whether it would have stayed at /home/vagrant if I had not moved it.
However, after destroying and up-ing the machine again, the file was lost. Vagrant destroy and your backup file (Step 4–5) After creating the database backup (in the root of the vagrant machine /home/vagrant) on the vagrant machine (before destroying it), I thought to be smart and moved it (with sudo mv) to the directory where my code is mapped (/home/vagrant/Code). If your backup file is still there, run: mysql -u homestead -psecret ). Now checkout the latest tagged release using git checkout. Again in this directory (assuming you have cloned the homestead repo when you installed this the first time), fetch the repo.From the same directory: vagrant destroy.From the directory where Homestead is installed, run the update command: vagrant box update (this may take a while, because a large file download takes place).
I copied the backup to my machine (just to be sure it is not gone after the destroy in step 4): scp -P 2222.
0 kommentar(er)
