TODO - what about in Windows? [installation of the vagrant/virtual box/git bash (shell)]
Raptor Man
I am happily digging around in R on R in my 5 year old laptop for Mac. I then decided to run my windows box ... but hit something which stumped me nearly immediately. The section in bold. I know there were probably more windows users at the first two lessons. I wasn't one of them that time. I ran the three steps on your getting started and they all went off without a hitch ... minus what appeared to be a permissions error at first (RPC is serving fine). It might be a permissions error still, and I would normally cowboy through bash/git/vagrant/virtual machine.
The catch being I have no idea that, should I cowboy through - will the lessons and gem etc run like they are expected further down the line.... so I look up a ton of files and am unsure of what would fix it without sabotaging the windows expirement :)
I found the .bash config file, the git config file and read 5 pages of stackoverflow (some still over my head):
http://stackoverflow.com/questions/6883760/git-for-windows-bashrc-or-equivalent-config-files-for-git-bash-shell
http://git-scm.com/book/en/Customizing-Git-Git-Configuration
http://yuilibrary.com/yui/docs/tutorials/git/
Along with the documentation on vagrant:
http://docs-v1.vagrantup.com/v1/docs/getting-started/
Per the instructions, I spent an hour or more pouring over in vagrant, I just install the files and *bam* I can change into the railsmn-dev-box and vagrant up.
Thus where it all goes wrong:
Step 2 - Build Vagrant Virtual Machine
In the terminal application,
git clone git://github.com/railsmn/railsmn-dev-box.git
cd railsmn-dev-box
vagrant up
TODO - what about in Windows? ... does anyone recall what to do about windows? I really appreciate all the help in the labs, just something I botched by not attending the first class and now, I need that bit :)
Reading from the vagrant documentation says something about "path" ... from what vague pieces I can recall path is show by the shell in unix or "~" etc ... and I think that I can just path: <something>\<whatever>\<morestuff> if my experiences in unix transfer to the open bsd or whatever bastard step child mac runs on ... sadly though whatever wrapper or object they use has slightly different handling, which basically makes my unix like speaking Cantonese on an island nearly 100 miles away from home.
Still, the question ... will it blow up or snicker off in even more hard to find errors - which will take hours to find because you guys weren't around to see what I did?
Install Vagrant
To install Vagrant, download the appropriate package or installer from the downloads page, and install it using standard operating system procedures. On Windows and Mac OS X, the vagrant command should automatically be placed on your PATH. On other systems, you must add /opt/vagrant/bin to your PATH.
Raptor Man
http://comments.gmane.org/gmane.comp.tools.vagrant/216
The fix is to find the stable 4.2.12 instead of using the broke June release 4.2.14 off oracle's page.
I haven't finished the down load yet ... but here is the link to the old version that is the supposed fix:
https://www.virtualbox.org/wiki/Download_Old_Builds_4_2
