I know this isn't the ideal setup but its the way we're using right now: The repository is checked out to the website's dev site root (i.e. /var/www/html). Code is modified and commited here. It's easy because you can make your changes, refresh - and see that change instantly. Not exactly possible if we all check out locally or something... We're using TortoiseSVN and it seems that when we commit, it changes the properties of the entries file inside of .svn to owner of the person committing. If another person makes a change to the same file and tries to commit it, it fails. Surely/hopefully there is SOMETHING we can do to deal with this? Thanks!
your doing things inverted mate.. standard approach: single svn repo all users checkout from svn repo and check in changes etc (as per normal) then.. option 1: small commit hook script that exports the contents of svn to the domain option 2: have the site as checked out version of the repo aswell, then you can simply svn up from the site root for the local copy. I'd go with option 2, then you can change files manually on the server and commit them from there as well