RE: [PHP] web site source control

Dreamweaver has a simple check-in/check-out facility built into its FTP client. All of our designers use this at my insistence. Although this doesn't keep a revision history, it does keep us from stepping on each other's changes. We also have a separate server where we set up web sites in development, and only upload changes to the live server when they are completed and reviewed. At some point in the (hopefully near) future we will set up a CVS repository. I think it is just as important to maintain a revision history on pure HTML documents, and I think your typical editor/designer can be trained to use CVS and convinced of its importance. > From: kev [mailto:kevin.porter@fast.no] > > Hi, > > We have quite alot of source code to look after for our web site now, > and I'm looking at putting it all in a CVS repository. Being new to CVS > I am unsure of a few things. I thought I would ask you guys on this list > how you go about source control for websites. Do you bother with a > source repository at all? > It has become a logistical nighmare keeping files in sync on development > and production machines, especially since we have more than one > programmer as of recently. Also, one of our editors sometimes changes a > few PHP files because they contain content - that is the other problem, > there is no clear divide between content and code, so how do I decide > which files should be in the repository? I don't want to put files in > which the editors need to change regularly because there is no way I > will be getting them to check files out of a repository, that would be > way beyond them. > So, how do you guys tackle these problems? > > thanks, > > - Kev