For my case, whenever I create a folder under /opt/lampp/htdocs and if the name is same with ‘path/to/repo’ , it will cause this error message:

Error: PROPFIND request failed on ‘/reponame’ 
Error: PROPFIND of ‘/reponame’: 301 Moved Permanently (http://www.vancouvereasy.com) 

Fortunately, Apachefriends project provides a development package so that I can take advantage of it to re-compile the PHP. My Linux version is CentOS 4.5 final, all the steps are pretty straightforward:

1) Download latest apachefriends packages (both working package and development package) and install them.
2) Download PHP 5.2.5 and untar it
3) yum install pspell-devel
4) Download libbz2 and install it
5) Hack the PHP configuration
    
   This is the original apachefriends’s php configuration

./configure –prefix=/opt/lampp –with-apxs2=/opt/lampp/bin/apxs –with-config-file-path=/opt/lampp/etc –with-mysql=/opt/lampp –enable-inline-optimization –disable-debug –enable-bcmath –enable-calendar –enable-ctype –enable-dbase –enable-discard-path –enable-exif –enable-filepro –enable-force-cgi-redirect –enable-ftp –enable-gd-imgstrttf –enable-gd-native-ttf –with-ttf –enable-magic-quotes –enable-memory-limit –enable-shmop –enable-sigchild –enable-sysvsem –enable-sysvshm –enable-track-vars –enable-trans-sid –enable-wddx –enable-yp –with-ftp –with-gdbm=/opt/lampp –with-jpeg-dir=/opt/lampp –with-png-dir=/opt/lampp –with-freetype-dir=/opt/lampp –without-xpm –with-zlib=yes –with-zlib-dir=/opt/lampp –with-openssl=/opt/lampp –with-expat-dir=/opt/lampp –enable-xslt=/opt/lampp –with-xsl=/opt/lampp –with-dom=/opt/lampp –with-ldap=/opt/lampp –with-ncurses=/opt/lampp –with-gd –with-imap-dir=/opt/lampp –with-imap-ssl –with-imap=/opt/lampp –with-gettext=/opt/lampp –with-mssql=/opt/lampp –with-sybase=/opt/lampp –with-interbase=shared,/opt/interbase –with-mysql-sock=/opt/lampp/var/mysql/mysql.sock –with-oci8=shared,instantclient,/opt/lampp/lib/instantclient –with-mcrypt=/opt/lampp –with-mhash=/opt/lampp –enable-sockets –enable-mbstring=all –with-curl=/opt/lampp –enable-mbregex –enable-zend-multibyte –enable-exif –with-bz2=/opt/lampp –with-sqlite=shared,/opt/lampp –with-libxml-dir=/opt/lampp –enable-soap –enable-pcntl –with-mysqli=/opt/lampp/bin/mysql_config –with-mime-magic –with-pgsql=shared,/opt/lampp/postgresql –with-iconv –enable-dio –with-pdo-mysql=/opt/lampp –with-pdo-pgsql=/opt/lampp/postgresql –with-pdo-sqlite –with-ming=shared,/opt/lampp

Because we only use MySQL , so I remove other database support from it such as:

–with-pdo-pgsql=/opt/lampp/postgresql
–with-pgsql=shared,/opt/lampp/postgresql
–with-oci8=shared,instantclient,/opt/lampp/lib/instantclient
–with-interbase=shared,/opt/interbase

Of course, in order to support Pspell extension, add this at the end

–with-pspell=/usr

6) re-compile the php

Done!   

1) I use SSH remotely access the server, after I input the password, it took me about 20 seconds to login in.
2) some clients complained that they could not access the website whereas others could.

After dinner, I came across my friend’s home, in his computer, the website could not be accessible.

Then, I was thinking … he used different ISP, the ip address in his computer starts with 64 whereas mine starts with 24.

I login the server again and type "ip route" and found there was an entry forward all ip start with 64 to one special ip address.(who set this?)

After I deleted this ip route, the two problems above are gone!

Here is the config file:

### This file controls the configuration of the svnserve daemon, if you
### use it to allow access to this repository. (If you only allow
### access through http: and/or file: URLs, then this file is
### irrelevant.)

### Visit http://subversion.tigris.org/ for more information.

[general]
### These options control access to the repository for unauthenticated
### and authenticated users. Valid values are "write", "read",
### and "none". The sample settings below are the defaults.
 anon-access=read
 auth-access=write
### The password-db option controls the location of the password
### database file. Unless you specify a path starting with a /,
### the file’s location is relative to the conf directory.
### Uncomment the line below to use the default password file.
 password-db=passwd
### The authz-db option controls the location of the authorization
### rules for path-based access control. Unless you specify a path
### starting with a /, the file’s location is relative to the conf
### directory. If you don’t specify an authz-db, no path-based access
### control is done.
### Uncomment the line below to use the default authorization file.
# authz-db = authz
### This option specifies the authentication realm of the repository.
### If two repositories have the same authentication realm, they should
### have the same password database, and vice versa. The default realm
### is repository’s uuid.
# realm = My First Repository

———————-

Solution is very simple, just remove the SPACE in front of lines which are not be commented.

Writing a remote executable SSH command in post-commit script of the SVN system. After every commit, the system will automatically put all files to two different hosts. The two hosts can be located in two different cities, even two different countries.

Then I had him went through all the options tab, nothing was wrong.

Eventually, I found the problem is the filter, go view -> Current View, you will get what I mean.

What gave me a great impression was the author’s friend Joe Fitzpatrick said "No one cares if you can back up–only if you can recover."

Definitely, I truly believe it because it happened a lot of  around us. The company in the next door backed up their data by tape. What a coincidence! The tape they used have trouble to be reloaded while the hard drives in the server die. The reason is quite  simple — this tape has been used every night during the past three years.

Under /repository name/hooks/, there is a file called post-commit.tmpl, it is a template file that you can revise it to fit your needs.

Upon the requirements from programmers, I have implemented two post commit scripts:

1) the website and the SVN server  reside in the same machine
2) the website and the SVN server  reside in two different machine

Rename the Folders.dbx file: