Should .vagrant/machines/{machine}/aws/synced_folders be checked into source control?

[Jay Weisskopf]

I'm working on a git repo where the original authors have checked in .vagrant/machines/{machine}/aws/synced_folders. Inside is JSON data that contains absolute paths that are only applicable to a specific machine, (e.g. some "hostpath" values are "/Users/author/foo/bar..."). Is this file supposed to be checked in? I figured Vagrantfile is the source of truth and this other file is just for caching some kind of local state, but I wanted to double-check before removing it.

Thanks,

Jay

[Jamie Jackson]

Yeah, don't version that. .vagrant is created on vagrant up. I only version my Vagrantfile and and any provisioning scripts it references (and any other custom files/folders that you might need).

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/ce105684-9eef-41d3-b04a-c44270ba5656%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Alvaro Miranda Aguilera]

yup

.vagrant is local to each computer, so you can just delete

send a PR and add that to .gitignore :)