For what it's worth, that's exactly how I handle my dev environments. Samba share on a VMware machine configured the same as the server. The samba share is taken from subversion (eg, a local working copy) and I can manage commits even from windows systems. I also have the advantage of having the same software installed as on the production server, so less chances of different behavior on each end. MySQL is kept up-do-dte via replication from the live server.
Issac Jeff Armstrong wrote: > -------- Original Message -------- > Subject: Re:32 & 64 bit memory differences > From: Mark Maunder <[EMAIL PROTECTED]> > To: Octavian Rasnita <[EMAIL PROTECTED]> > CC: modperl@perl.apache.org > Date: 05 November 2007 06:32:11 > >> I wouldn't recommend doing dev on windows for a linux environment. >> Dual boot your machine with Ubuntu linux and use that instead. It'll >> save you a lot of time and headaches. > > > Or even make yourself a virtual PC using MS Virtual PC and install a > Linux / Apache / Modperl / Samba / MySQL / SVN etc into it (e.g. Debian > is easy, or whatever you need for your prod). > > Put samba on the virtual linux box so you can edit code directly using > your fav PC editor. Each developer gets his own Linux environment, which > he can cart around on laptops etc, and can bounce apache without killing > anyone else etc. And once you have made one virtual Linux box, it is > easy to clone it. > > Jeff
