-
Notifications
You must be signed in to change notification settings - Fork 189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug in box_check_update code #237
Comments
I totally get the |
Also not sure how this ever worked. Also apologies - I'm a GitHub n00b (this was my first ever PR!) so my fault if I messed something up or not understanding how something works. I manually made this change today in my local machine's Vagrantfile.erb because this is killing me, and things are working as expected. |
@rayterrill congrats on your first PR! Don't worry everyone is a beginner at some point; and we all gain experience at different rates. Welcome and please continue to contribute, we are all better because you are here. |
:+100: to what @jjasghar said |
See im still learning to emoticon! |
Thanks all! |
The "box_check_update" section of code in templates/Vagrantfile.erb is resulting in the quoted value of whatever you've entered (true/false) to be transferred to the Vagrantfile, and it isn't working correctly (i.e. false becomes "false", which is not the same as false).
Validated that removing the quotes from the Vagrantfile manually results in the correct behavior in Vagrant - it no longer checks for an updated box on a 'vagrant up'. This is probably just as simple as removing the quotes, like:
Backstory: We're behind a proxy and using Windows, so these kind of things kill us. :(
The text was updated successfully, but these errors were encountered: