svnserve --version
- 没有安装的话安装subversion，直接用yum 安装
yum install -y subversion
svn --version
mkdir /www/server/svn
mkdir /www/svnconfig
分别添加4个文件
#!/bin/bash
echo -e "\n"
read -t 30 -p "请输入仓库名称:" NAME
echo -e "\n"
#echo "仓库名称为:NAME"
#NAME=oa
PATH="/www/server/svn/NAME"
if [ -d "PATH" ];then
echo -eNAME"仓库已经存在\n"
exit 1
fi
/usr/bin/svnadmin create PATH
/bin/cp /www/svnconfig/svnserve.confPATH/conf/
/bin/cp /www/svnconfig/post-commit PATH/hooks/
echo -e "export LANG=zh_CN.UTF-8 \n\n/usr/bin/svn update /www/wwwroot/NAME --username svn --password aseghwiotghoisdhagoih --no-auth-cache \n\nchown -R www:www /www/wwwroot/NAME">>PATH/hooks/post-commit
if [ -f "/www/wwwroot/NAME/.user.ini" ];then
/usr/bin/chattr -i /www/wwwroot/NAME/.user.ini
fi
echo -e "["NAME":/] \n@itwork=rw \n*=\n\n">>/www/svnconfig/authz
/usr/bin/svn checkout svn://127.0.0.1/NAME /www/wwwroot/NAME --username svn --password aseghwiotghoisdhagoih --no-auth-cache
echo -e "\n"
/bin/chown -R www:www /www/wwwroot/NAME
echo -e "目录创建成功\n"
### This file is an example authorization file for svnserve.
### Its format is identical to that of mod_authz_svn authorization
### files.
### As shown below each section defines authorizations for the path and
### (optional) repository specified by the section name.
### The authorizations follow. An authorization line can refer to:
### - a single user,
### - a group of users defined in a special [groups] section,
### - an alias defined in a special [aliases] section,
### - all authenticated users, using the 'authenticated' token,
### - only anonymous users, using the 'anonymous' token,
### - anyone, using the '*' wildcard.
###
### A match can be inverted by prefixing the rule with '~'. Rules can
### grant read ('r') access, read-write ('rw') access, or no access
### ('').
[aliases]
# joe = /C=XZ/ST=Dessert/L=Snake City/O=Snake Oil, Ltd./OU=Research Institute/CN=Joe Average
[groups]
# harry_and_sally = harry,sally
# harry_sally_and_joe = harry,sally,&joe
itwork = svn,svn2
# [/foo/bar]
# harry = rw
# &joe = r
#*=既是所有人为空权限
# * =
# [repository:/baz/fuz]
# @harry_and_sally = rw
# * = r
#[www.baidu.com:/]
#itwork=rw
#*=
### This file is an example password file for svnserve.
### Its format is similar to that of svnserve.conf. As shown in the
### example below it contains one section labelled [users].
### The name and password for each user follow, one account per line.
[users]
# harry = harryssecret
# sally = sallyssecret
svn = xxxxxxx
svn2 = xxxxxxx
#!/bin/sh
# POST-COMMIT HOOK
#
# The post-commit hook is invoked after a commit. Subversion runs
# this hook by invoking a program (script, executable, binary, etc.)
# named 'post-commit' (for which this file is a template) with the
# following ordered arguments:
#
# [1] REPOS-PATH (the path to this repository)
# [2] REV (the number of the revision just committed)
#
# The default working directory for the invocation is undefined, so
# the program should set one explicitly if it cares.
#
# Because the commit has already completed and cannot be undone,
# the exit code of the hook program is ignored. The hook program
# can use the 'svnlook' utility to help it examine the
# newly-committed tree.
#
# On a Unix system, the normal procedure is to have 'post-commit'
# invoke other programs to do the real work, though it may do the
# work itself too.
#
# Note that 'post-commit' must be executable by the user(s) who will
# invoke it (typically the user httpd runs as), and that user must
# have filesystem-level permission to access the repository.
#
# On a Windows system, you should name the hook program
# 'post-commit.bat' or 'post-commit.exe',
# but the basic idea is the same.
#
# The hook program typically does not inherit the environment of
# its parent process. For example, a common problem is for the
# PATH environment variable to not be set to its usual value, so
# that subprograms fail to launch unless invoked via absolute path.
# If you're having unexpected problems with a hook program, the
# culprit may be unusual (or missing) environment variables.
#
# Here is an example hook script, for a Unix /bin/sh interpreter.
# For more examples and pre-written hooks, see those in
# the Subversion repository at
# http://svn.apache.org/repos/asf/subversion/trunk/tools/hook-scripts/ and
# http://svn.apache.org/repos/asf/subversion/trunk/contrib/hook-scripts/
REPOS="1"
REV="2"
mailer.py commit "REPOS" "REV" /path/to/mailer.conf
##WEB=/www/wwwroot/www.baidu.com
#WEB=/www/wwwroot/
#export LANG=zh_CN.UTF-8
#/usr/bin/svn update WEB --username svn --password 1111 --no-auth-cache
#chattr -iWEB/.user.ini
#chown -R www:www $WEB
### 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.apache.org/ for more information.
[general]
### The anon-access and auth-access options control access to the
### repository for unauthenticated (a.k.a. anonymous) users and
### authenticated users, respectively.
### Valid values are "write", "read", and "none".
### Setting the value to "none" prohibits both reading and writing;
### "read" allows read-only access, and "write" allows complete
### read/write access to the repository.
### The sample settings below are the defaults and specify that anonymous
### users have read-only access to the repository, while authenticated
### users have read and write access to the repository.
# anon-access = read
# auth-access = write
anon-access = none
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 directory containing
### this configuration file.
### If SASL is enabled (see below), this file will NOT be used.
### Uncomment the line below to use the default password file.
# password-db = passwd
password-db = /www/svnconfig/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 the
### directory containing this file. 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
authz-db = /www/svnconfig/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
### The force-username-case option causes svnserve to case-normalize
### usernames before comparing them against the authorization rules in the
### authz-db file configured above. Valid values are "upper" (to upper-
### case the usernames), "lower" (to lowercase the usernames), and
### "none" (to compare usernames as-is without case conversion, which
### is the default behavior).
# force-username-case = none
[sasl]
### This option specifies whether you want to use the Cyrus SASL
### library for authentication. Default is false.
### This section will be ignored if svnserve is not built with Cyrus
### SASL support; to check, run 'svnserve --version' and look for a line
### reading 'Cyrus SASL authentication is available.'
# use-sasl = true
### These options specify the desired strength of the security layer
### that you want SASL to provide. 0 means no encryption, 1 means
### integrity-checking only, values larger than 1 are correlated
### to the effective key length for encryption (e.g. 128 means 128-bit
### encryption). The values below are the defaults.
# min-encryption = 0
# max-encryption = 256
svnserve -d -r /www/server/svn
- 进入svn配置目录,执行add.sh
./add.sh