[Fwd: [thelist] ftp and vss]

Chris George chrisgeorge at home.com
Thu Oct 19 23:07:27 CDT 2000

Hi... this is the first I've seen of this thread, but thought I'd be able to
offer my 2 cents...

We use CVS as our version control package.  It's quite capable, runs on Mac,
PC, Linux (and probably others).  CVS was chosen around 4 years ago by the
Java programmers, and has proved to be quite capable with Dreamweaver,
Homesite and BBedit, our "Big Three".

Our method is the same as described below.  Our staging server is where all
the development gets done.  We 'check in' to that server, and when it's
ready to go live, we 'check out' to the www server (handled by one person).
It works very, very well, and forces us to come up for air before it goes

And yes, the FTP was completely locked out.  It takes a little getting used
to, but boy/girl what a difference.

Anyway, hope it might help a little.


----- Original Message -----
From: "Jay Turley" <jay at weberrific.org>
> We ran into a similar problem with VSS at McDonnell Douglas.
> the best solution we could come up with was to make every developer
> *completely aware* that they *had* to follow the procedures for publishing
> to the production site.
> Depending on how far you are willing to go with this, however, there are a
> couple of things you could try. First, you could implement a policy of
> completely uploading the site to the production server periodically
> (weekly? daily?). The first time that this wipes out some "bright spark"'s
> work, they will become painfully aware of their failure to follow
> publishing procedure. However, this may end up ruining some needed
> work/correction and possibly savagely irritating your clients. :( Second,
> if you have a staging and a production server, you could end up doing what
> we eventually did. Everyone has rights to muck, with the staging server
> they want. But only "you" would have the ability to take code to the
> production server. However, you're gonna need a beeper for those weekend
> emergencies when someone needs code put out fast. Of course, this helps
> test your code first. Third, lock down your FTP site so noone but you has
> the password and don't publish through VSS.

More information about the thelist mailing list