search

datadryad / vagrant-dryad

Vagrant and Ansible config for building a (v1) Dryad VM
0 stars 4 forks source link

recreating #24 #45

Closed daisieh closed 7 years ago

daisieh commented 8 years ago

This PR replaces #24.

daisieh commented 8 years ago

We waited too long and now I don't understand how this is supposed to work and both @dleehr and @rnathanday are gone :(

dleehr commented 8 years ago

What's the question? I think the intent was to create a subdirectory in the vagrant dir called sync, that would pull in the VM's dryad-repo and /opt/dryad directories.

That way, you could view logs and and edit code from the .../vagrant-dryad/sync directory on your host computer (e.g. mac running virtual box) and they would be in sync with the operative directories inside the VM.

I never used the sync though, but I assume @rnathanday did.

dleehr commented 8 years ago

I can do a skype or hangout if that would help.

ghost commented 8 years ago

If I remember correctly, the main reason this was useful to me was to allow me to work in the VMs source tree (/home/vagrant/dryad-repo) using an IDE from my Mac.

The /opt/dryad mount was less useful, but helped in debugging and working with the application's deployed files from my Mac without a complete rebuild (esp. the XSL and JS files). Doing that risks accidentally overwriting modified files after a rebuild, so I tended to use links between /opt and /home if a lot of files would change.

daisieh commented 8 years ago

@rnathanday, do you remember where I was supposed to be creating the sync directory in relation to the vm?

ghost commented 8 years ago

The way it is configured now, it will use the sync/ directory in the root of this repo, so 'vagrant-dryad/sync/'. The 'create: false' flag is default for vm.synced_folder and will cause provisioning to fail if the sync/ directory is not in place, iirc. (https://docs.vagrantup.com/v2/synced-folders/basic_usage.html)

I vaguely recall there being an issue with setting 'create: true' and letting vagrant create the directory rather than the user, but I don't remember what it is now -- it possibly had to do with user permissions or with undesired automatic cleanup. It is clunky for the synced_folder to be required but not automatically created, so I wish I had made a note of it.

ghost commented 8 years ago

There is a default shared folder from 'vagrant-dryad/' on the host machine to '/vagrant' on the guest machine, so if this PR is causing issues it can be worked around without doing away with synced folders entirely.

I am not certain, but I think that Vagrant may not stay fully compatible with VirtualBox as their respective versions change, at least when the host machine is OSX. I have been seeing issues around this lately on another project.

ryscher commented 8 years ago

Note to myself... merge this, but set the create=true, and see what problem arises.