You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If using Windows, when issuing "vagrant up", you're bound to run into issues with the .sh scripts that get ran at the start where the environment path is set. This may be an issue pulling from github into github for windows, or how the files were initially saved.
My solution was to open the scripts in sublime text (with user settting set: "default_line_ending": "unix"), and save a new file over itself. This will use unix style line endings for the files, and the problem should resolve.
The text was updated successfully, but these errors were encountered:
This post is to help those on Windows.
If using Windows, when issuing "vagrant up", you're bound to run into issues with the .sh scripts that get ran at the start where the environment path is set. This may be an issue pulling from github into github for windows, or how the files were initially saved.
My solution was to open the scripts in sublime text (with user settting set: "default_line_ending": "unix"), and save a new file over itself. This will use unix style line endings for the files, and the problem should resolve.
The text was updated successfully, but these errors were encountered: