-
Notifications
You must be signed in to change notification settings - Fork 21
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
Fix Vagrantfile for Vagrant 1.3.4 using 'Vagrant.configure('2') syntax #4
base: master
Are you sure you want to change the base?
Conversation
Vagrant fixed a bug in version 1.3.5 which allows I think my master will now be a head of yours. I may send another pull request. |
Hi @gregelin |
Tested, everything works. Regarding the PR. ...i think i'll cherry pick the changes to the vagrant file you made. if that's ok with you. |
That is fine. Do you still me need me to make the readme changes? And redo the pull request? Sent from my iPhone Greg Elin
|
Nope, i'll do it. Thanks for your help updating the project. Really appreciate it. |
Thanks for the work you did! Our mission at GitMachines is to make it easy for innovators to bring open source and new tech into security-minded institutions. Out goal is to create accreditation-ready configurations. CKAN is a tech/project identified as high value. Sent from my iPhone Greg Elin
|
The Vagrantfile was failing with Vagrant 1.3.4. This Vagrant file works.
However, I could not get the hostname directive to work, even after changing the syntax to
hostname
fromhost_name
. I finally just commented. Whenever thevagrant up
was run with the host name directive uncommented, the VM would be created and the provision would never run.