vagrant - Using one puphpet config for both osx & win -


is possible puphpet configs have code directory change according host os?

i can done actual vagrant file, can't see how yaml.

i've attempted add qualifying field yaml:

    synced_folder:         e6zs5esfmosx:             owner: ''             group: ''             source: '/users/user/development/www'             target: /var/www             sync_type: osx             rsync:                 auto: 'false'         e6zs5esfmwin:             owner: ''             group: ''             source: 'i:\development\www'             target: /var/www             sync_type: win             rsync:                 auto: 'false' 

and alter vagrant file switch accordingly:

elsif folder['sync_type'] == 'osx'         config.vm.synced_folder '#{folder['source']}', "#{folder['target']}", id: "#{i}", type: 'nfs' 

but still gives error i:\development\www not being available when attempting vagrant within osx.

what best way fix this? remove folders yaml , manually define them in vagrant file? means there little bit of work every time generate new config using puphpet. not bad, seems me there should easier way.

you can override settings inside config.yaml config-custom.yaml file. create new file , change blocks you'd like.

deep_merge used, need change blocks want, , not include want keep default.

aside that, can edit vagrantfile include more config files depending on host os.


Comments

Popular posts from this blog

c# - Validate object ID from GET to POST -

node.js - Custom Model Validator SailsJS -

php - Find a regex to take part of Email -