Tracking Your Deployed Files

…posted by davidjmedlock:

If you’re not using some sort of version control, you should be. “Why,” you ask? “Why not,” is my reply.

Most of us do not have access to a dedicated ColdFusion server. If you’re like me, you have a developer’s copy of CFMX on your computer at home (or whereever your development takes place). I also have CVS installed on my machine for keeping track of my code. It doesn’t allow me to easily deploy it to my server, since I have to actually FTP it to my host, but at least I can keep track of it on my machine.

Also, I tend to keep a log of files I’ve deployed and the date that I deployed them to a live server. This way I can, at a glance, look at my log and see where to look if there’s a problem.

For an easy tutorial on how to use CVS for your site, I recommend Harry Fuecks’ CVS tutorial.

For Windows users who don’t want to deal with command line CVS, you can use one of many graphical interfaces for CVS:


CVS Web Client (No Longer Supported by Developer)

Tortoise CVS

You can find more GUI’s and tools at the CVS Web Site.

Keeping track of each version of your code can save you a lot of headaches and heartaches later on when all of a sudden you need to revert back to an older version very quickly.

Win an Annual Membership to Learnable,

SitePoint's Learning Platform

  • pete

    I always suggest RCS for the lone developer, it’s much easier for a novice to use over CVS…

  • Tony Brandner

    Curious about other CF developers experiences with CVS. I really pushed CVS in my company (wanting to stay open source). The other developers here thought it was so difficult to get up and running, and integrate it within our development environment, that we’re now moving towards SourceSafe. Any comments?

    Tony Brandner

  • davidjmedlock


    When I got my first development job I had no experience with source control whatsoever. In fact, I had “known” ColdFusion itself for no more than a week.

    At that company, they had taken great pains to keep their application flexible, stable, well-planned (as well as possible), and they used CVS due to its open source nature. I managed to pick it up pretty quickly and eventually even wrote a web-based interface for CVS using ColdFusion.

    I’ve yet to use SourceSafe. If the company already has the license for SS, I’d say go for it. If you paid for it you should use it. And maybe it is easier, I don’t really know. If the company doesn’t have another version control system, CVS is an excellent option in my opinion. Yes, it’s got a bit of a learning curve. But there are trade offs in everything.

    The real issue behind it all is not which version control system you use but that you actually use one. Your time and code are too valuable to take risks with when it comes to simple matters such as tracking your code.