I went through the setup of each client project the same … following the example project instructions all the way … so they were both created in the same order … each is individual and self contained so not sure why I would need to run reload in that instance … the example with Trellis is because he is using one vagrant machine for multiple projects no?
Even with that said though … I did in fact already try that last night … not the re-provision, but, just the reload … I will try the reprovision as well right now …
I was under the impression that it was standard practice to be able to have multiple project machines at any given time but I’m thinking that perhaps browsersync isn’t set up to see multiple hosts at localhost:3000 and it’s retaining only the first entered host name for whatever reason because no matter what I do I can vagrant up my first machine/project and gulp watch just fine but just can’t get the second one to load~ That’s all that seems logical to me but again … I’m so new to all the little bits and bobs in the gooey center of ansible/gulp/vagrant and the playbooks etc. that I am clueless to troubleshoot at any respectable level yet
My environment looks like this:
.git is set to push to remote private github repo and my deploys will all be via ansible only … even if I have to deploy production files locally and copy up to my centos server because I don’t have a playbook set up for centos yet due to my meak skills at the moment~
.git is set same as above to it’s own private repo but will deploy to DigitalOcean droplet ( have already successfully gone through the whole process on this one )