My two cents,
It's not bad, but you need to be aware of collisions. We set it up
with a folder for each developer and it contains the main application
code.
The upside is that we each have our own code base so we don't affect
each other when cutting new code. The downside is that we can each
have the same file checked out and be working on it. The trouble comes
when one deb checks in the file, as occasionally it will duplicate
some lines in the code. It can lead to some funky errors.
Otherwise, the only other error is the dispatcher going down and not
passing the updates in. This does affect all users as the queue gets
backed up until the dispatcher is turned back on.
Bastien
Sent from my iPod
On Feb 5, 2009, at 21:06, "TG" <tg-php@xxxxxxxxxxxxxxxxxxxxxx> wrote:
So, for my purposes.. after trying a handful of solutions.. open
source and
commercial.. I think I've decided that Reliable Software's "Code Co-
op"
is what's going to work best for me.
My trial is almost up, so as soon as my next paycheck comes, I think
I'll
be purchasing the full version for $150.
For me, it's totally worth it. It stores everything in a local
database,
but allows collaboration if that's what you're into. Via email for
the
$150 version, via LAN for the $200 version.
It lets me add files by type, is easy to check out files. Anyway.. if
anyone's looking for an easy Windows version control system, check
it out.
(no, I don't work for them, just passing along the recommendation
since I'm
digging this software)
Thanks for all the input!
-TG
----- Original Message -----
From: "TG" <tg-php@xxxxxxxxxxxxxxxxxxxxxx>
To: php-general@xxxxxxxxxxxxx
Date: Wed, 31 Dec 2008 11:40:23 -0500
Subject: [PHP] Question about version control.. sorta..
Ok.. so I know about CVS and SVN and unfortunately haven't had as
much
experience with them as I'd like. I've used them, but always in a
really
basic sense and always on systems that have already been set up. A
friend
recently mentioned GIT ( http://git.or.cz/ ) too.
But here's my situation.. I deal with dozens of clients. I
usually make
a
backup copy of their site (at least the files, not usually the DB)
so I
have the latest copy of the site to make changes to. Usually I'm the
only
one working on the site, but sometimes other people may make
changes too.
Not so often than we're conflicting with our changes, or if this is a
known
issue, we make sure to coordinate.
What I'd ideally like to do is be able to use a CVS type system to
keep
incremental backups of the code. So instead of checking code out
of CVS,
changing it, then checking it back in... I'd like to just do a mass
checkin
of the whole site and have changes recorded and the ability to look
at
previous versions with DIFF and all that. And of course the
ability to
'check out' a previous set of files by date or revision maybe.
I assume you can do this with one of the major version control
systems,
but
mostly what I see with how to use these systems involves checking
code
out
then checking it back in. That's not really what I want to do.
The other issue is that I run Windows. So if there's something
nice and
WinGUI, that'd be nice. Please no "you should be running linux"
responses. I don't have anything against Linux or Mac, they're great
systems. But I have my reasons for running Windows.
Also, I realize this is semi-OT for a PHP list, but asking on a CVS
list
or a
SVN list might not give me the more comprehensive/broad experience
base
I'm
looking for. I'd like a semi-unbiased response. :)
Thanks in advance!
-TG
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP Windows Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
