My changes to Homestead.yaml are not reflected in the virtual environment after I vagrant up

Question

I edited the shared folder mapping rules in my Homestead.yaml file (C:\Users\username\.homestead). Then, I entered "vagrant halt" command to shut down vagrant. Then, I entered "vagrant up".

However, the edits that I made to the folder mapping are not reflected in the virtual environment. It's as if my changes were not made at all in the Homestead.yaml file.

How do I make the vagrant virtual environment reflect the changes that I made to the Homestead.yaml file?

score 7 · Accepted Answer · edited May 21 '20 at 06:21

7

You should reload using

vagrant reload --provision

edited May 21 '20 at 06:21

Yevgeniy Afanasyev

37,872
26
173
191

answered Aug 15 '16 at 02:37

Paul Vidal

403
2
6

score 1 · Answer 2 · edited May 21 '20 at 05:59

1

Please do not vagrant destroy, there are many things involved. If your vagrant is still running do vagrant provision, if it is not do vagrant up --provision. If things don't work as expected, check your file mappings for mistakes.

edited May 21 '20 at 05:59

Yevgeniy Afanasyev

37,872
26
173
191

answered Aug 15 '16 at 03:48

Oladipo

1,579
3
17
33

To add to your answer, here is a definitive guide on homestead.yaml, just have a view to avoid many beginners errors. https://abbasharoon.me/homestead-yaml-explained-a-z/ – Metabolic Nov 01 '16 at 21:01

score 0 · Answer 3 · edited May 21 '20 at 07:25

0

I should have used vagrant destroy instead of vagrant halt after updating my homestead.yaml file.

edited May 21 '20 at 07:25

double-beep

5,031
17
33
41

answered Aug 15 '16 at 00:25

Colin Hu

189
2
14

2

`vagrant halt`. Edit Homestead.yaml then `vagrant up --provision` – Qevo Aug 15 '16 at 01:08

My changes to Homestead.yaml are not reflected in the virtual environment after I vagrant up

3 Answers3

Linked