在centos7下安装svn

### 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
### 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
### 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 [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
### 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
### 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
### 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. means no encryption, means
### integrity-checking only, values larger than are correlated
### to the effective key length for encryption (e.g. means -bit
### encryption). The values below are the defaults.
# min-encryption =
# max-encryption =

### 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

jiangbo =

zhangsan =

lisi =

wangwu =

### 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 # [/foo/bar]
# harry = rw
# &joe = r
# * = # [repository:/baz/fuz]
# @harry_and_sally = rw
# * = r

[groups]
# 产品经理组
pm = jiangbo
# 开发人员组
dev = zhangsan,wangwu
# 菜鸟组
rookie = lisi

[/]
# 表示项目径路组有更新和提交的权限
@pm = rw
# 表示开发组只有更新的权限
@dev = r
# 表示 李四 这个用户自由更新的权限
lisi = r

[version_test_n:/]
# 表示该版本库下面所有用户都有更新和提交的权限
* = rw

#!/bin/bash
# THIS FILE IS ADDED FOR COMPATIBILITY PURPOSES
#
# It is highly advisable to create own systemd services or udev rules
# to run scripts during boot instead of using this file.
#
# In contrast to previous versions due to parallel execution during boot
# this script will NOT be run after all other services.
#
# Please note that you must run 'chmod +x /etc/rc.d/rc.local' to ensure
# that this script will be executed during boot. touch /var/lock/subsys/local

svnserve -d -r /www/version_test_2/

[Unit]
Description=Subversion protocol daemon
After=syslog.target network.target[Service]
Type=forking
EnvironmentFile=/etc/sysconfig/svnserve
ExecStart=/usr/bin/svnserve --daemon --pid-file=/run/svnserve/svnserve.pid $OPTIONS[Install]
WantedBy=multi-user.target

vi /etc/sysconfig/svnserve

systemctl enable svnserve.service

ps -aux | grep 'svn'

###
### 基础操作
###
svn checkout(co) - 检出
# 检出一个版本库(/目录) (并且带有用户名和密码)
ex : svn co svn://127.0.0.1(/dir) (--username jiangbo --password 123456)
svn add - 添加到版本控制
# 添加一个index.php二进制文件到版本控制(并未提交到版本库)
ex : svn add index.php
# 添加一个pic.png树文件到版本控制(并未提交到版本库)
ex : svn add pic.png
# (递归)添加一个css目录及下面所有文件夹和文件到版本控制(并未提交到版本库)
ex : svn add css
# (未递归)仅仅添加js目录(未包含下面任何文件夹和文件)到版本控制(并未提交到版本库)
ex : svn add js --non-recursive
svn commit(ci) - 提交修改到服务端(创建一个新版本号)
# 提交一个index.php二进制文件到版本库并添加注释
ex : svn ci -m "this is index.php" index.php
# 提交一个index.php二进制文件到版本库但不想添加注释，由于 svn ci 命令必须包含注释，只能将注释留 "" 来到达这个需求了
ex : svn ci -m "" index.php
# 提交一个pic.png树文件到版本库并添加注释
ex : svn ci -m "this is pic.png" pic.png
# (递归)提交一个css目录及下面所有文件夹和文件到版本版本库并添加注释
ex : svn ci -m "this is css dir" css
# 提交当前目录版本控制下的所有文件目录及文件
ex : svn ci -m "" *
svn update(up) - 更新工作副本
# 更新当前目录的工作副本
ex : svn up
# 将index.php二进制文件更新至版本1
ex : svn up -r index.php
# 强制更新当前目录到最新版本
ex : svn up *
svn delete(del,remove,rm) - 从版本库中删除文件和目录
# 删除index.php二进制文件到版本控制(并未提交到版本库)
ex : svn rm index.php
# 删除pic.png树文件到版本控制(并未提交到版本库)
ex : svn rm pic.png
# (递归)删除css目录及下面所有文件夹和文件到版本控制(并未提交到版本库)
ex : svn rm css
svn diff(di) - 比较当前工作副本和最新版本库之间的差异
# 比较当前工作副本中的index.php和最新版本库中的index.php之间的差异
ex : svn di index.php
# 比较当前工作副本中的index.php和版本库版本2中的index.php之间的差异
ex : svn di -r index.php
# 比较版本库版本2中的index.php和版本库版本3中的index.php之间的差异
ex : svn di -r : index.php
# 比较当前工作副本和最新版本库所有文件目录和文件之间的差异
ex : svn di
svn mkdir - 创建一个文件夹到版本控制中
# 创建 doc 文件夹到版本控制中
ex : svn mkdir doc
->- mkdir doc
->- svn add doc
svn cat - 在不检出的情况查看文件内容
# 查看 svn://ip/index.php 文件内容
ex : svn cat svn://ip/index.php
svn revert - 工作副本进行还原操作
# 工作副本中的index.php还原至最新版本库中的index.php
ex : svn revert index.php
# 将工作副本所有文件目录和文件还原至最新版本库
ex : svn revert *
# (递归)将工作副本所有文件目录下文件和文件还原至最新版本库
ex : svn revert --recursive *
###
### 冲突及冲突解决办法
###
svn resolve - 弹出冲突解决选项
# 现有index.php冲突了，必须解决它，弹出选项
ex : svn resolve index.php
-> Select: (p) postpone(推迟), (df)show diff(显示差异), (e) edit file(编辑文件), (m) merge(合并), (mc) my side of conflict(采用我的文件), (tc) their sidee of conflict(采用他的文件), (s) show all options(显示所有选项): mc(并且告知svn服务器冲突已处理)
-> Resolved conflicted state of 'index.php'(冲突已解决，采用我的文件)
# 需要提交解决了的冲突文件至版本库中
svn ci -m "" index.php
->Sending index.php
->Transmitting file data .
->Committed vevision (old+).
# 冲突已经完美解决了，但是我们需要避免冲突，再编写程序或者其他什么操作之前更新至最新版本
###
### 加锁和解锁机制(不推荐使用)
###
svn lock - 加锁
# 将当前工作副本中的index.php加锁至版本控制中
ex : svn lock index.php
# 此时别人不能操作文件
# 如果修改index.php提交至版本库中，则会自动解锁。但是如果一直未改变该文件也未去解锁的话就会造成项目组其他人一直不能操作该文件，比如该人员辞职了，那么后果你可以想想，所以建议避免使用
svn unlock - 解锁
# 将当前工作副本中的index.php解锁至版本控制中
ex : svn unlock index.php
# 提交解锁文件
# svn ci -m "" --no-unlock index.php

# 步骤1: 创建svn多项目管理配置文件目录
mkdir /var/svn
# 步骤2: 创建svn配置文件目录
mkdir /var/svn/svnconfig
# 步骤3: 创建第一个项目
svnadmin create /var/svn/pigeonfan
# 步骤3: 创建第二个项目
svnadmin create /var/svn/mall
# 步骤3: 创建第三个项目
svnadmin create /var/svn/hardware
# 步骤4: 拷贝任意一个项目conf文件目录下所有文件至svn配置文件目录
cp /var/svn/pigeonfan/conf/* /var/svn/svnconfig/
# 步骤5: 删除svn配置文件目录的svnserve.conf
rm -f svnserve.conf
# 步骤6: 修改/var/svn/svnconfig/passwd文件
# 步骤7: 修改/var/svn/svnconfig/authz文件
# [groups]
# admin_group=admin
# [pigeonfan:/]
# @admin_group=rw
# *=
# [mall:/]
# @admin_group=rw
# *=
# [hardware:/]
# @admin_group=rw
# *=
vim /var/svn/svnconfig/authz
# 步骤8: 修改pigeonfan、mall、hardware下面的svnserve.conf，统一修改成
# anon-access = none
# auth-access = write
# password-db = /var/svn/svnconfig/passwd
# authz-db = /var/svn/svnconfig/authz
# 建议修改一个进行覆盖替换即可
# cp -f /var/svn/pigeonfan/svnserve.conf /var/svn/mall/svnserve.conf
# cp -f /var/svn/pigeonfan/svnserve.conf /var/svn/hardware/svnserve.conf
vim /var/svn/pigeonfan/svnserve.conf
vim /var/svn/mall/svnserve.conf
vim /var/svn/hardware/svnserve.conf
# 步骤9: 重启svn服务器
svnserve -d -r /var/svn

### 如果后续有需要继续添加更多版本库的话
# 步骤1: 创建一个新的版本库
svnadmin create /var/svn/newrule
# 步骤2: 复制覆盖掉新的版本库中的svnserve.conf文件
cp /var/svn/pigeonfan/conf/svnserve.conf /var/svn/newrule/conf/svnserve.conf
# 步骤3: 将/var/svn/svnconfig/authz文件添加权限
# [newrule:/]
# @admin_group = rw
# * =

### 可能会用到一些常用指令
# 查看服务
netstat -tnlp
# 查看svn服务启动没有
ps -aux|grep svn
# 如何清除SVN保存的用户和密码
rm ~/.subversion/auth/svn.simple/*
# kill掉svn进程(-9强制的意思)
kill -9 1131
# 重启svn服务(-d作为服务后台进行运行)(-r将后面的目录作为svn运行的根目录)
kill -9 1131 # 先强制kill调svn进程
svnserve -d -r /var/svn # 然后启动svn服务进程