lib/vagrantomatic/instance.rb
def add_shared_folder(folders)
      folders=Array(folders)
      # can't use dig() might not be ruby 2.3
      if ! @config.has_key?("folders")
        @config["folders"] = []
      end


      # all paths must be fully qualified.  If we were asked to do a relative path, change
      # it to the current directory since that's probably what the user wanted.  Not right?
      # user supply correct path!
      folders.each { |folder|
        if ! folder.start_with? '/'
          folder = "#{Dir.pwd}/#{folder}"
        end

        @config["folders"] << folder
      }
    end
def add_shared_folder(folders)
      folders=Array(folders)
      # can't use dig() might not be ruby 2.3
      if ! @config.has_key?("folders")
        @config["folders"] = []
      end


      # all paths must be fully qualified.  If we were asked to do a relative path, change
      # it to the current directory since that's probably what the user wanted.  Not right?
      # user supply correct path!
      folders.each { |folder|
        if ! folder.start_with? '/'
          folder = "#{Dir.pwd}/#{folder}"
        end

        @config["folders"] << folder
      }
    end
Add a new folder to @config in the correct place.  Folders must be
 specified as colon delimited strings: `HOST_PATH:VM_PATH`, eg
 `/home/geoff:/stuff` would mount `/home/geoff` from the main computer and
 would mount it inside the VM at /stuff.  Vagrant expects the `HOST_PATH`
 to be an absolute path, however, you may specify a relative path here and
 vagrantomatic will attempt to extract a fully qualified path by prepending
 the present working directory.  If this is incorrect its up to the
 programmer to fix this by passing in a fully qualified path in the first
 place