Thanks for both of your replies, I appreciate this is only "tangentially
related to komodo". 
SubVersion is something I've never used, so any info you provided has been a
great help.

When using Komodo with Subversion, how does the checkout/checkin procedure
work, and when/how do we issue commit commands etc?

If anyone can help me off the komodo list with some of the server side
options I would appreciate it greatly. Particularly file access, I currently
use samba to access the files, but does this have to change when using
subversion with Komodo?

Simon
-----Original Message-----
From: Jeff Griffiths [mailto:jeffg@[...].com] 
Sent: 29 April 2008 21:23
To: David Brewer
Cc: komodo_aspn@stiplady.net; komodo-discuss@[...].com
Subject: Re: [Komodo-discuss] Komodo with SubVersion

I agree generally with David, and have added some comments:

David Brewer wrote:
...
>   * 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 use Apache and DAV/SVN as well, both internally and externally with the
Open Komodo repository. I also use it (a bit) on my own site. Setup can be a
bit tricky but if you have any questions let me know. I think accessing SVN
using https and a self-signed cert is realy handy. You can even do tricks
like allow read-only access to the world and restrict write access to
authenticated users.

>   * We're using FSFS rather than the Berkley DB backend.

@David: what is the advantage there?

>   * 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.

+1, and this is where svn:ignore rules come in handy, without having to
do a bunch of fiddling with file systems.

As well, there is a great script included with the subversion source 
package called 'svn-load-dirs.pl'. I use this tool to manage different 
versions of external source trees; I originally came across it here:

http://www.davidgrant.ca/maintaining_vendor_sources_with_subversion

JeffG


_______________________________________________
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