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
To simplify the Ansible/Vagrant issue I created a basic provisioner which outputs the vagrant file to wherever you like. You can then run Ansible or Debops outside of Vagrant as normal. Using a custom provisioner means you don't need to create a dummy playbook, vagrant won't try to run Ansible at all and you can specify where you want the inventory to be created, so you don't have to use symlinks. It also means you don't have to deal with port numbers and ssh keys like you would with a hand-crafted inventory file.
I haven't yet fixed the issue of it running for each machine defined in the Vagrantfile , but doing so doesn't hurt anything and is easy to work around.
The text was updated successfully, but these errors were encountered:
To simplify the Ansible/Vagrant issue I created a basic provisioner which outputs the vagrant file to wherever you like. You can then run Ansible or Debops outside of Vagrant as normal. Using a custom provisioner means you don't need to create a dummy playbook, vagrant won't try to run Ansible at all and you can specify where you want the inventory to be created, so you don't have to use symlinks. It also means you don't have to deal with port numbers and ssh keys like you would with a hand-crafted inventory file.
I haven't yet fixed the issue of it running for each machine defined in the Vagrantfile , but doing so doesn't hurt anything and is easy to work around.
The text was updated successfully, but these errors were encountered: