Good news - was able to test on another Mac (10.9.2) and a Windows (8.1)
laptop -- VirtualBox, Vagrant, and the VM work. I have not done much
testing *inside* the VM except creating a new rails app, starting it,
and loading
http://localhost:3000 from the host.
For Windows, the only thing we *need* Git Shell for is an installation
of `ssh` in the user`s PATH; all the Vagrant commands work from the
Windows "Command Prompt" (I have no idea what the proper place to tell
people to find this is; I had to go into the Start screen and go to
Search). So it may be worth reviewing that later to see if there's a
less intrusive way to get SSH on student machines. (We should also
change `cd ~` to just `cd` so that it works on both Unix-like systems
and Windows-without-bash-of-some-sort.)
I also tested accessing the VM by opening VirtualBox and running it,
er, head-ful... that works OK, but even bold blue is hard to read, the
default console resolution is tiny, and there are confusing messages
about keyboard grabbing and mouse support that cover up the login
prompt. I really think we should avoid recommending that anyone use the
VM this way and save it for a last resort in cases where they can't use
`vagrant ssh`. If there's some common setup that will continue to need
it, creating an additional non-Vagrant VM image may be the way to go
so they could at least have a nice gnome-terminal.
Other stuff to maybe note: Windows will ask about allowing firewall
access for the local machine -> VM connection, so students should be
warned they will need to allow this. It probably looks different on
older Windows versions though.
> --
> You received this message because you are subscribed to the Google Groups "RailsBridge Boston Alumni" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
railsbridge-boston...@googlegroups.com.
> For more options, visit
https://groups.google.com/d/optout.
>
--
things change.
dec...@red-bean.com