Re: Ideal Subversion Setup

Hi David,

We're doing the same type of work, web development on numerous projects.

We just starting using Coda, which accesses the repo via http and then
we use a post-commit hook to auto checkout the latest files from our
repo to our central web root for previewing. I like this approach
because it means we're all looking at the same version of the site on
the web site and it's dramatically less setup for new projects. (Not
to mention not having to support Apache issues on developer machines)

Basically we work from one big repo for all of our projects, each of
which is in a folder.

/ourRepo
        /client1
        /client2
        /client3

Then in apache we have 1 site, which has a wildcard DNS record pointed
at it so that anything at a certain sub-domain points at that box.

eg. *.dev.resolutionim.com

so we could do: client1.dev.resolutionim.com, client2.dev.resolutionim.com
, etc.

In our Apache .conf file for that site, we have a mod_vhost_alias that
takes the first subdomain 'client1, client2, etc' and changes the web
root to that particular folder in our master web root.

/devWebRoot
        /client1
        /client2
        /client3

It works quite well for us so far.

--
Brendan Farr-Gaynor
On 2009-12-16, at 11:00 AM, David Burleson wrote:
> Hi Everyone,
>
> I have been using subversion with TortoiseSVN for a couple of years  
> now. I work in a team of 3 web developers on multiple websites. Im  
> starting to wonder if the way we use subversion and version control  
> is the correct way. So, I have posted to ask advice on the best way  
> to use Subversion in a web development team with multiple projects.
>
> We currently each have our own development area on a local web  
> server for each project. We also each have our own SVNcheckout of  
> each project. Once we have checked out/updated our 'repo' we drag  
> the contents over to our development area to work. Once we are  
> finished working, we drag the files back over to our 'repo' and  
> commit it.
>
> I have a feeling that the better process is to make your development  
> area the SVNcheckout. My only problems is how subversion and  
> TortoiseSVN handle symlinks and file/dir permissions. We have a  
> couple of symlinks for folders like 'images' so we don't have to  
> duplicate the directories on the webserver and some folders which we  
> upload files too have 777 permissions and what not. I don't know if  
> subversion or TortoiseSVN will pass these own and treat the symlink  
> as a symlink and not a folder, and pass the permission into the  
> 'repo' too.
>
> I would greatly appreciate any feedback on the ideal setup for this  
> occasion as I'm looking for ways to streamline our development  
> process.
>
> Please note that im not a regular user of mailing lists, so I  
> apologise if I have/haven't done something correctly to post this  
> email to the list.
>
> Best Regards,
> David