Question

I m New to SVN and have Trialed with it local on my/2002/2host testters (The has a Subversion “one-click-install” function).

找到了我围绕功能Im 无限期出售的路,但利用它管理我的工作网站(不是由梦想主办,因此没有提供一波的SVN安装)。

我正确地认为,我可以在我的网站根基(包含所有档案)上建立一个存放处,然后当我开发新的特征和作出一项承诺时,这将更新我的网站? 这是否是此类事情的适当工作流程?

如果是的话,在我的边远服务器上打上这种事情是否有标准的方法?

感谢。

Answer 1

为了使网站内容的更新自动化,请查阅网站post-commit hook/a>。

邮政管理处 Hooks的运行经过了变革,成功地向SVN存放处承诺。因此,你也许可以在网站的根基上 h起特别志愿人员网。

Answer 2

如果我正确理解你的问题,你就重新尝试利用颠覆作为你的地方发展环境与生产环境之间的中介。您希望在一个单独的地点建立网站,进行变革,然后将这些变化传播到你的制作网站。如果这一说法不正确,请作出答复。

这当然是可行的。为了正确使用术语,在颠覆活动中,你有一个“保存”在你的颠覆服务器上。你们永远不会触及存放处本身,除非是间接地利用一个救助客户开展业务。您可以“核对”存放处的多份“工作副本”(或其中的子版),以便查阅你的来源档案。为了实现你再次提出的要求,你将制作一份有关你的开发机器的工作副本,并在那里进行改动。如果满意,你会“承诺”给你的存放处。在您的生产地点,您必须另外制作同一存放地点的工作副本。你们需要在这份工作文件中明确提出“最新消息”,以便对其适用最新的修改。修改不会自动向所有工作复制件传播。

如果你有点,你就应当花时间阅读。这是一种极其宝贵的资源,用于颠覆和整个来源控制原则。

Answer 3

Both of the previous answers are good information. But there are a couple of issues that I thought a good idea to present. Should you go with the post-commit-hook idea I would suggest that the script to be made smart enough to only do the deploy when you specifically wish it too. To have the script do a deploy on every commit would be very restrictive and force you to forego many of the advantages of using source control.

One idea would be a keyword trigger in the comment that the script could use to trigger a deploy to production. Another would be to deploy only when the script determines that the commit is to a new tag folder.

Setting up the prodcution system as a local working copy and using SVN UPDATE does not have the problem of deploying commits that might not be ready for deployment to production, but suffers from not being as automatic. To solve that issue you could create a script the runs periodically on the production system that examines the repository in much the same way that a continous integration system like Crusie Control or Team City does and periodically examine the repository for a new commit and then do the update.

In either case I would suggest that you build the script smart enough to only deploy from a new TAG folder. That way you can use source control for all of the advantages that it brings and only deploy when you create a new TAG folder.

友情链接