Use the vagrant home path to store the nfspaths file. #85
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
I think its a good idea. I'll test this a bit and, if nobody has any counter-arguments, will merge it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I propose to store the
nfspathsfile in the vagrant home path instead the installation directory.The advantage of this is less permission headaches on windows.
If Vagrant is installed in the "Program Files" folder you might run into issues writing into that folder due UAC oder directory owner ship (TrustedInstaller).
Writing in the vagrant home directory should be possible since by default it's a directory within the Windows user directory - which is writeable by the current user.
This could solve following issues: