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
Genesis used to have a ./bin/provision script that ran the Ansible playbooks from within the machine. This made it really easy to port over to Windows (there are a few other changes I had to make to genesis but nothing major); however, Ansible is completely unsupported on Windows.
I guess my question is what would be the appropriate script to run all this from within Vagrant?
The text was updated successfully, but these errors were encountered:
Because there are several steps that ansible handles transparently (some as part of the vagrant provision process), I don't know that this would work on windows...but you could try bringing the machine up without provisioning:
vagrant up --no-provision
And then run the playbooks manually from within the vm as the vagrant user:
Ah! That's what I was asking, how I could run this within the VM. I'll test this out and let you know! :) I've got the original Genesis working locally (except for capistrano/ruby nightmare) so when I migrate over to evolution, I'll try to document what I had to do!
Genesis used to have a
./bin/provision
script that ran the Ansible playbooks from within the machine. This made it really easy to port over to Windows (there are a few other changes I had to make to genesis but nothing major); however, Ansible is completely unsupported on Windows.I guess my question is what would be the appropriate script to run all this from within Vagrant?
The text was updated successfully, but these errors were encountered: