Home/ Questions/Q 297173
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T06:36:56+00:00

we’re currently investigating SVN at work – having escalated our practices to include a

  • 0

we’re currently investigating SVN at work – having escalated our practices to include a fair bit of development. I have to confess, we’re finding the remote setup process rather tricky, none of our team is that conversant with Linux/SSH.

My question is, how many of you you administer your own remote SVN repository versus using a 3rd party solution like Beanstalk?

An additional question:
Do you use your remote SVN to commit changes to a live site, or do you use plain ‘ole FTP to upload and reserve SVN simply for versioning?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I’m using private repositories instead of third-parties, works great. SVN+Apache can be a bit tricky, but using svn+ssh is pretty straightforward:

    1. Install your repo in for example /var/svn/repo/.
    2. Create a group all the committers are members of, for example “svn”.
    3. cd /var/svn/repo
    4. chgrp -Rc svn . # Change all files to the svn group
    5. find type -d -print0 | xargs -0 chmod +s # Set sticky bit on all directories to keep group on new files

    That’s all you need to do. Your repo address is now

    svn+ssh://user@host/var/svn/repo

    You can also create a symlink in the root directory to make it shorter:

    $ cd /
$ ln -sv /var/svn/repo .

    By doing that, you repo address is now

    svn+ssh://user@host/repo
    • 0