Closed ghost closed 8 years ago
Thanks, the synced folders are great, and this will certainly make it easier to edit code/debug from the host.
There's a handful of issues though
First, the directory that contains the Vagrantfile
is already synced to the vm at /vagrant
. So everything would get duplicated there on the VM. If you look in /vagrant
you'll see them synced there too.
Some possible workarounds:
bootstrap-dryad.sql
is synced over this way but that's on its way out (See #8)Vagrantfile
to a vagrant subdirectory (I did this in dplace-vagrant)And a couple other minor things:
.gitignore
dsynced_folder
makes sense for the Amazon EC2 provider. That was added upstream. Probably just need to put these in the config.vm.provider "virtualbox" do |vb, override|
block.I had noticed the /vagrant share, but hadn't thought about the duplication issues. I'm not sure how heavy-weight it is, though, given that (presumably) the subdirectories are on the FS as a link or mount instead of taking up virtual drive space. Not having had any use for the /vagrant drive yet, I would probably be inclined to disable it, but that is only based on my usage to this point and not based on any of the setup that is being done.
The Vagrantfile in my fork has your VB and gitignore items implemented (updated here).
Thanks for catching the override error -- fixed. The README is also updated to mention the sync configuration.
These changes are now in #45.
Added two config.vm.synced_folder entries to enable a couple of useful guest directories to be available from the host system.
This config does not create any directories on the host or guest system, so before 'vagrant up' is run, the host directories (./sync/...) must be created. Vagrant warns and exits if the local directories are not present.