1.需求描述在Centos系统中搭建svn服务器环境2.搭建过程2.1 yum安装svn[root@localhost /]# yum install svn? 2.2 新建目录存储svn目录[root@localhost /]# mkdir /usr/svn2.3 新建测试仓库pro[root@localhost /]# s...

1.需求描述 在Centos系统中搭建svn服务器环境 2.搭建过程 2.1 yum安装svn 2.2 新建目录存储svn目录 [root@localhost /]# mkdir /usr/svn 2.3 新建测试仓库pro [root@localhost /]# svnadmin create /usr/svn/pro 进入到目录/usr/svn/pro展开目录 说明: hooks目录:放置hook脚步文件的目录 locks目录:用来放置subversion的db锁文件和db_logs锁文件的目录,用来追踪存取文件库的客户端 format目录:是一个文本文件,里边只放了一个整数,表示当前文件库配置的版本号 conf目录:是这个仓库配置文件(仓库用户访问账户,权限) 2.4 进入到文件夹conf,配置相关信息 展开文件夹conf,有以下文件 对上述三个文件配置内容如下:(粉红色标记部分为修改) vi passwd ### This file is an example password file for svnserve. [users] admin =admin1 vi authz ### This file is an example authorization file for svnserve. [aliases] [groups] # [/foo/bar] # [repository:/baz/fuz] 以下是说明: admin = admin1 创建admin组,组成员为:admin1 user = qinys 创建用户组,用户成员:qinys [/] 赋予根权限,为了便于管理和权限的控制,可以把权限细化到版本库中相应的目录 @admin = rw admin组有读写的权限 @user = r user组只有读的权限 *= 表示除了上面设置的权限用户组以外,其他所有用户都设置空权限,空权限表示禁止访问本目录,这很重要一定要加上。 vi svnserve.conf ### The anon-access and auth-access options control access to the [sasl] 2.5 启动svn [root@localhost /]# svnserve -d -r /usr/svn/ 2.6查看启动情况 ps -ef | grep svn 停止svn,使用命令:kill –9 20181 即可20181为进程ID 2.7 windows客户端连接 客户端下载地址:https://tortoisesvn.net/downloads.html 根据本地系统选择版本下载即可 下载完成后安装,安装完成后到D盘根目录下右键 点击【OK】 出现这个问题的原因是由于防火请问题造成 那么我们如何处理呢?我们为svn指定端口,然后在指定区域开放此端口 执行以下命令 firewall-cmd --permanent --zone=public --add-port=3690/tcp 接着就打开防火请并查看状态 systemctl start firewalld systemctl status firewalld 再添加3690端口 firewall-cmd --permanent --zone=public --add-port=3690/tcp 接着重启防火墙 firewall-cmd --reload
### 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.
# harry = harryssecret
# sally = sallyssecret
qinys = 123456
### 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
### ('').
# joe = /C=XZ/ST=Dessert/L=Snake City/O=Snake Oil, Ltd./OU=Research Institute/CN=Joe Average
# harry_and_sally = harry,sally
# harry_sally_and_joe = harry,sally,&joe
# harry = rw
# &joe = r
# * =
# @harry_and_sally = rw
# * = r
admin = admin1
user = qinys
[/]
@admin = rw
@user = rw
*=
### 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 = none #注意前边不要有空格,要顶齐 .匿名访问权限,可以是read,write,none,默认是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
### 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
本文标题为:【svn】Centos搭建svn服务器环境


基础教程推荐
- 通过StatefulSet部署有状态服务应用实现方式 2022-10-01
- windows环境下apache-apollo服务器搭建 2023-09-10
- P3 利用Vulnhub复现漏洞 - Apache SSI 远程命令执行漏洞 2023-09-10
- Apache CarbonData 1.0.0发布及其新特性介绍 2023-09-11
- Centos 安装Django2.1 2023-09-24
- Docker容器操作方法详解 2022-11-13
- Centos7 nginx的安装以及开机自启动的设置 2023-09-22
- 为Win2003服务器打造铜墙铁壁的方法步骤 2022-09-01
- RFO SIG之openEuler AWS AMI 制作详解 2022-12-28
- Apache Kafka 2.5 稳定版发布,新特性抢先看 2023-09-11