It is definitely possible to do this, although this is really only
tangentially related to Komodo.  Where I work we do most of our work
on Ubuntu virtual machines, with all of our work checked into
subversion repositories.  The initial transition can be painful but
once you do it you'll wonder how you ever worked any other way.
Komodo will act as a client to your repository, but to be honest I
still prefer other clients such as TortoiseSVN (on Windows) or the
command line.

The most difficult part of setting up subversion for someone who is
new to it is choosing from the bewildering variety of ways to set up
such a system.  Subversion is a very flexible tool and gives you
plenty of opportunities to do things the wrong way.

I would recommend starting small to get a handle on the concepts and
then scaling up.  Doing some reading in advance will probably save you
a lot of time in the long run.

Some possibly useful books:
 * Pragmatic Version Control: Using Subversion by Mike Mason.  This
isn't a great reference book for the advanced user, but it is short
enough to be approachable as a good introduction to the subject.
 * Producing Open Source Software: How to Run a Successful Free
Software Project by Karl Fogel.  Not only about version control, but
has a great discussion of best practices for version control on open
source projects.  These ideas are applicable in other contexts as
well.
 * If you haven't found it already, http://svnbook.red-bean.com/ is a
good place for detailed information about Subversion.

The shop I work for does work for multiple clients as well.  For what
it's worth, here are some of the decisions we made:
 * We make a separate repository for each project.  Why?  So that if
necessary, we can archive an entire repository to recover its disk
space.
 * We access subversion through an Apache server, primarily to provide
external HTTPS access to the repositories.  This was possibly more
complicated to set up then the alternatives but works very well for
us.  We're actually using Apache on a Windows server for this purpose.
 * We're using FSFS rather than the Berkley DB backend.
 * Even with version control, you will still have your backup
issues... we do nightly backups of all the repositories.
 * We refrain from checking in large binary assets such as video or
photoshop files to the repository.  Subversion doesn't do a good job
of handling diffs to these files, which means that if you put these in
the repo it will swell in size dramatically.  There is no good way of
recovering this space if this happens, because deleting the file only
deletes it in the latest version of the repository.
 * Windows users use TortoiseSVN, which is an awesome SVN client for Windows.
 * We use the Trac issue-tracking system, which integrates with your
subversion repository to provide all kinds of neat information.

There's a whole new generation of version control software out there
which is probably technically superior to SVN.  But, especially if you
are primarily developing on Windows, SVN's ecosystem of related tools
like Tortoise and Trac is pretty hard to beat.

David

On Tue, Apr 29, 2008 at 11:10 AM,  <komodo_aspn@[...].net>  wrote:
> 
> 
>  Hi All,
> 
>  I'm not sure I can do what I'm thinking of doing...
> 
>  After some previous disasters I now keep regular backups of all my work,
>  every 5 minutes I backup any changed files from all of my projects, and
>  every night I then take a complete backup. But over time this is taking a
>  horrendous amount of space.
> 
>  What I was thinking of doing is installing Subversion, or some other version
>  control software, and using the inbuilt versioning so that I can monitor
>  changes in files. I currently develop on Windows Vista using Komodo, all
>  files are stored on my linux (CentOS) server, and all the projects (99%) are
>  web based projects so I need Apache to also be running under the same
>  environment. I work on websites for multiple clients, and these all run
>  under seperate Apache VirtualHosts.
> 
>  Is it possible for me to use Komodo / SubVersion / Apache in this way?
> 
>  Is anyone using this type of setup? How difficult was it to setup?
> 
>  Thanks in advance for any comments you can give me.
> 
>  Regards,
> 
>  Simon
>  _______________________________________________
>   Komodo-discuss mailing list
>   Komodo-discuss@[...].com
>   To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
>   Other options:
>  http://listserv.ActiveState.com/mailman/listinfo/Komodo-discuss
> 
> 
_______________________________________________
Komodo-discuss mailing list
Komodo-discuss@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Other options: http://listserv.ActiveState.com/mailman/listinfo/Komodo-discuss