I'm maybe a little unclear on exactly what you want. It says Version Control in the subject, but then PHP debugging and such is discussed below. To me the two are independent subjects. So, some more general info...
For version control I'd suggest either CVS or Perforce, depending on budget :) CVS is obviously free, and is quite good. You definitely want to run the server portion of it on a UNIX/Linux box, but you can use it quite easily from Windows with WinCVS or you can probably integrate CVS commands into your editor (depending on your editor/IDE). Perforce is a superb source code management tool, but it costs money (although it's price is reasonable). It has some nice features over CVS (such as the whole atomic checkin process, which once you use/work this way, you'll be bummed that they don't all have it - I heard CVS 2 may do this if that ever happens). You can get Perforce for free if you only have 2 (or less) users. It works very well on Windows and has a nice GUI. You can also run the server on Windows NT/2000. Just about any version control system will work for your PHP, HTML, CSS, and any other source code you have. Basically they're all text files, and that's where these systems work best because they can help with merges and diffing and obviously keep track of differences between revisions. You can do your development work on any platform and use typically UNIX/Linux or Windows for a server for source control, deployment, etc. Version control is just that, it is up to you how you employ it in terms of your development environment. I would think most people use it most strictly for version control, and have scripts on their staging and/or deployment system where they pull a snapshot of code down, do a "build" (which may be compiling CGI scripts, or may just mean copying the files to the appropriate place on the server), and then fire up the server. Your developers would do similar things, just on their own machine (I assume they have a similar environment setup as the deployment, e.g. they're running a web server with mod_php or whatever). Hope that helps. -----Original Message----- From: John Lim [mailto:[EMAIL PROTECTED]] Sent: Monday, November 19, 2001 10:57 AM To: [EMAIL PROTECTED] Subject: [PHP] Re: Version Contol for PHP site Hi Jeff There is a Windows version of WinCVS (see http://wincvs.org/ ). John Jeff Bearer <[EMAIL PROTECTED]> wrote in message 1006195598.1407.7.camel@jbearer">news:1006195598.1407.7.camel@jbearer... > Hello, > I'm trying to come up with a workable solution to implement version > control for our site. I have developers that use windows, and don't > know too much about the unix command line, so I'd prefer to use a > windows client to work on the site if possible. > > I'm looking into CVS for the version control and I've found some > directions on how to use it with websites. But it only talks about > static HTML development, it doesn't say how developers would debug PHP, > CGI, etc. This solution would not give them any ability to debug their > code before checking it back in. > > I suppose if I could get them all comfortable with the UNIX command > line, they could work on the development server, checking out the files > to a working directory that is also a virtual host. > > A new idea that I just came up with would be to have the developers use > VNC viewer to connect to an X server on the development box. The > deveopers could use a X GUI for CVS to check it out, and edit files etc. > and keep the working directory a virtual host like above. > > Is anybody doing something like this with their PHP development? Any > direction from a working implementation would be great. And what do you > think about the VNC idea that I just came up with? > > -- > Jeff Bearer, RHCE > Webmaster > PittsburghLIVE.com > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED] -- PHP General Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
