41–49 of 49 posts
Windows Seven w/ Ubuntu running in a VM. It would be 100% windows but faking all the server-side components got too tough.
I haven't used VM software for ages. Do you get good enough performance on virtualized Ubuntu to do all your developing?
It's also worth noting that the pole permits more than one selection, which defeats the purpose of asking, "What is your primary development system".
From my experience VirtualBox is faster and more reliable than Vmware.
Windows Seven w/ Ubuntu running in a VM. It would be 100% windows but faking all the server-side components got too tough.
I haven't used VM software for ages. Do you get good enough performance on virtualized Ubuntu to do all your developing?
Running two systems on your laptop is a perfectly viable strategy for dev machines, and if you're most at home in Windows, I recommend it. If you're Linux or OS X, though, I think it's probably worth the effort to keep your dev environment cross-platform instead of working on it in a VM.
Earlier quoted context omitted.
Yes. It turns out 12GB of RAM does come in handy. (I have the same setup, Win7 w/ Ubuntu VM). What's more annoying is doing port mapping through VirtualBox's XML configuration files, but this is a one-off task and not too complex. I'm seriously considering purchasing Mac OS X Server edition and using that in a VM as well but I can't figure out if this actually works. Does anyone know?
Just switch to Bridged networking in the VM and don't care about port mapping at all? (It will have its own IP.)
However, then I read this ServerFault thread and realised the bridge is a _new interface_, and hence you must either bind directly to it or bind to all interfaces in order to get your VM to become externally accesible!
http://serverfault.com/questions/206498/virtualbox-bridge-ne...
Fantastic!
Earlier quoted context omitted.
Just switch to Bridged networking in the VM and don't care about port mapping at all? (It will have its own IP.)
In case anyone else stumbled upon this thread, I've always thought running a VirtualBox VM in Bridged Networking mode still did not allow the VM instance to be externally accessible. However, then I read this ServerFault thread and realised the bridge is a _new interface_, and hence you must either bind directly to it or bind to all interfaces in order to get your VM to become externally accesible! http://serverfault…
And yeah, the reason something like AppEngine or Django wouldn't work is that they, by default, bind only to loopback/127.0.0.1, and are only accessible from the host on which they're running, as a security precaution.