Closed michaelsbradleyjr closed 10 years ago
@michaelsbradleyjr
I had a similar issue, but it's the same as specified in the Vagrant documentation:
Shared folders can be disabled by adding the disabled option to any definition:
Vagrant.configure("2") do |config|
config.vm.synced_folder "src/", "/srv/website", disabled: true
end
For example, my config looks like
config.vm.provider :rackspace do |rs, override|
rs.username = RS_USER
rs.api_key = RS_KEY
rs.rackspace_region = :lon
rs.flavor = /512MB Standard Instance/
rs.image = /CentOS 6.5/
rs.disk_config = "AUTO"
rs.rackconnect = true
rs.public_key_path = './keys/bootstrap.pub'
override.vm.synced_folder ".", "/vagrant", disabled: true
end
@michaelsbradleyjr @petems I think this should be fixed as long as you're using vagrant-rackspace 0.1.8+. It contained the feature:
Use new synced folder support found in Vagrant 1.4+ if available [GH-104]
If you're still using vagrant-rackspace 0.1.7, or if you're using Vagrant < 1.5 (the CHANGELOG says 1.4+ but I believe it was the rsync support is actually in 1.5) then vagrant-rackspace will be using a legacy rsync code so it won't be possible to "do your own thing".
@michaelsbradleyjr if you're able to upgrade, can you confirm the newer versions address your problem and close the issue?
@petems suggested workaround works for me (vagrant v1.6.3).
My
rsync
needs are different enough from the default actions of this plugin that I would like to toggle off that default behavior and do my own thing withconfig.vm.synced_folder ...
.How can I accomplish that? I searched around in the plugin's source code but it wasn't clear to me what I should do.
Thank you.