摘要:后自动同步到网站根目录的方法为什么需要同步呢原因是我们的文件其实是提交到了的仓库中,仓库不是一个实际的网站根目录。进入到项目下的文件夹把的扩展名去掉,并赋予权限。你的至此已经配置完毕,并且可以实现本地一执行上传,自动同步到网站跟目录。
前言 笔者服务器环境、目录情况:
系统:CentOS 6.5
网站根目录:/home/wwwroot/test/web
为什么要用svn?a.方便多人协作,查看成员工作内容和工作量。
b.即便是独自一人开发项目,也非常方便代码的部署(Sublime, Zend Studio都有svn的常见,配合快捷键,提交代码非常简单),同时可以找回历史版本的文件。
1.安装</>复制代码
yum install subversion
2.检查是否安装成功
</>复制代码
svnserve –version
3.创建仓库目录
</>复制代码
mkdir –p /home/svn/test
4.创建项目
</>复制代码
svnadmin create /home/svn/test
5.检查是否创建成功
</>复制代码
cd /home/svn/test
ll
如果成功,test目录下会多出几个文件夹
6.进入conf目录会看到3个配置文件,生成的文件中都有英文注释说明authz:用户权限配置
</>复制代码
### 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
[/]
testusername = rw
# [/foo/bar]
# harry = rw
# &joe = r
# * =
# [repository:/baz/fuz]
# @harry_and_sally = rw
# * = r
passwd:用户密码
</>复制代码
### 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
testusername =123456
svnserve.conf:
</>复制代码
### 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 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 = /home/svn/test
[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
7.启动SVN服务
svnserve -d -r /home/svn
注意:不是svnserve -d -r /home/svn/test
8.在本机安装TortoiseSVN输入svn://你的ip地址/test
如果弹出输入账号密码的对话框,表示上述设置正确。
9.Svn commit后自动同步到网站根目录的方法为什么需要同步呢?原因是我们commit的文件其实是提交到了svn的仓库中,svn仓库不是一个实际的网站根目录。流程如下:本地文件commit到仓库->仓库同步到根目录,可以把仓库理解为一个中转站。进入到项目下的hooks文件夹
</>复制代码
cd /home/svn/test/hooks
把post-commit.tmpl的扩展名去掉,并赋予777权限。然后vim post-commit写入如下内容。
</>复制代码
#!/bin/sh
export LANG=zh_CN.UTF-8
svn co svn://你的ip/test /home/wwwroot/test/web
# 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
重要步骤:然后cd /回到根目录,执行以下语句,这一步的作用是让服务器记忆你svn的账号密码,防止出现权限等问题,首先让你输入你服务器的密码,接着输入svn的账号密码,其中会问你是否记忆,输入yes。
</>复制代码
svn co svn://你的ip/test /home/wwwroot/test/web
至此svn已经配置完毕,并且可以实现本地一执行上传,自动同步到网站跟目录。
文章版权归作者所有,未经允许请勿转载,若此文章存在违规行为,您可以联系管理员删除。
转载请注明本文地址:https://www.ucloud.cn/yun/17402.html
摘要:前言最近在搭建服务器,用到了版本控制,在搭建过程中也遇到了好多问题,简单写一写步骤安装创建项目目录创建一个文件夹,用来存放一个或多个项目进入这个目录创建一个新的项目目录创建文件仓库这一步是让这个新的文件夹变成的版本库权限设置进入设置目录包 前言 最近在搭建服务器,用到了版本控制,在搭建过程中也遇到了好多问题,简单写一写 步骤 1、安装SVN $ sudo apt-get install...
摘要:免责声明本教程仅以个人经验撰写,未必适合所有系统环境。如在使用本教程途中,出现无法挽救的损失如数据丢失等,本人概不负责。本文最终服务器环境配置下面开始进入教程吧。教程结束本次教程本人在下搭建成功。 注意:本教程使用干净的 CentOS 7进行安装,如果您已安装其他环境或软件,涉及到内核升级,请您妥善备份,可能导致您已安装的软件不兼容或出现其他问题。 免责声明:本教程仅以个人经验撰写,...
摘要:免责声明本教程仅以个人经验撰写,未必适合所有系统环境。如在使用本教程途中,出现无法挽救的损失如数据丢失等,本人概不负责。本文最终服务器环境配置下面开始进入教程吧。教程结束本次教程本人在下搭建成功。 注意:本教程使用干净的 CentOS 7进行安装,如果您已安装其他环境或软件,涉及到内核升级,请您妥善备份,可能导致您已安装的软件不兼容或出现其他问题。 免责声明:本教程仅以个人经验撰写,...
阅读 3010·2021-10-19 10:09
阅读 3211·2021-10-09 09:41
阅读 3486·2021-09-26 09:47
阅读 2820·2019-08-30 15:56
阅读 662·2019-08-29 17:04
阅读 1055·2019-08-26 11:58
阅读 2579·2019-08-26 11:51
阅读 3451·2019-08-26 11:29