You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 13, 2023. It is now read-only.
I usually have multiple sites running inside a single instance.
When I add a new site, I add new entry to vagrant_synced_folders and a new entry to apache_vhosts in the config.yml file.
To get the new changes to apply I aways run a 'vagrant halt' and 'vagrant provision' command. But this feels like a bit overkill.
Is there an easier way to get the changes to apply?
The text was updated successfully, but these errors were encountered:
@thom8 is correct; you have to reload Vagrant to get synced folders working. If it's just a vhosts change/addition, you can just run vagrant --provision on a running instance.
Someday, I may have a faster method for certain kinds of config changes, but for now it does a full provision any time you want to change anything.
@geerlingguy we're working on a similar issue atm, it's mainly to support a new docker build but might provide some useful functionality to target specific roles/tasks.
I usually have multiple sites running inside a single instance.
When I add a new site, I add new entry to vagrant_synced_folders and a new entry to apache_vhosts in the config.yml file.
To get the new changes to apply I aways run a 'vagrant halt' and 'vagrant provision' command. But this feels like a bit overkill.
Is there an easier way to get the changes to apply?
The text was updated successfully, but these errors were encountered: