manaticr / manati-vm Goto Github PK

Falta limpiar archivos utilizados por este rol.

That's pretty much it.
I win @cienvaras.

There are a couple of issues to overcome in order to work in windows environments, the most important one is ansible that will never support windows as a Control Machine.

http://docs.ansible.com/ansible/latest/intro_windows.html#using-a-windows-control-machine

One possible solution is to check for the availability of the ansible-playbook and if it's not present in the host machine run the ansible from inside the VM, very much like drupal-vm does,

geerlingguy/drupal-vm#199
geerlingguy/drupal-vm#199 (comment)

The only other problem is the lack of good NFS support in windows, but using the virtual box filesystem solves the issue and as far as I understand vagrant will automatically switch to vboxfs when nfs is specified and not supported, but I could be mistaken and some action is required to achieve this.

The winnfsd project and similarly named vagrant plugin are still very unreliable and should not be recommended.
vboxfs does have a considerable performance penalty but seems to be the only reliable two way binding, SMB might be another but it needs to be explored.

Warning
Unicode library Standard PHP
Operations on Unicode strings are emulated on a best-effort basis. Install the PHP mbstring extension for improved Unicode support.

To ensure drush works!

It would be nice to add support for server aliases because sometimes we work with sites that have aliases, and even when we can update the vhosts manually, in the next provision we loose the changes, so I think it would be important to add the posibility to specify some server aliases for the sites created (and configure it so vhosts on apache or nginx include that info).

To avoid collisions and ensure ansible provisioner works always ok.

Ex. dev_config.vm.network "forwarded_port", guest: 22, host: 2104

Make it work!

[DEPRECATION WARNING]: Using the 'short form' for vars_prompt has been deprecated.
This feature will be removed in a
future release. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.

[WARNING]: Consider using file module with owner rather than running chown