你如何在 Subversion 中设置共享工作副本 [英] How do you setup a shared Working Copy in Subversion

查看:35
本文介绍了你如何在 Subversion 中设置共享工作副本的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我对 Subversion 还是很陌生.

I still very new using Subversion.

是否可以在网络可用共享 (c:\svn\projects\website) 上拥有一个工作副本,每个人(在本例中使用 3 个)都可以检出并提交文件?我们不需要构建服务器,因为它是一个 asp 站点,设计人员习惯于在保存文件时立即获得结果.我可以尝试向他们展示如何在他们的机器上本地设置它,但如果我们可以只在开发服务器上共享文件,并且仍然能够在有人完成时提交,那将是理想的.

Is it possible to have a working copy on a network available share (c:\svn\projects\website) that everyone (in this case 3 of use) can checkout and commit files to? We don't need a build server because it is an asp site and the designers are used to having immediate results when they save a file. I could try and show them how to set it up local on their machines but if we could just share the files on the development server and still have the ability to commit when someone is done, that would be ideal.

一个简单的解决方案是让我们所有人使用相同的 subversion 用户名,这至少可以让我将文件置于版本控制之下.

An easy solution would be for all of us to use the same subversion username and that would at least allow me to put files under version control.

但是是否可以从 svn 存储库中检出文件夹,但仍然需要每个人使用他们的用户/密码登录才能提交?

But is it possible to checkout a folder from the svn respository but still require each person to login with their user/pass to commit?

我正在尝试采用我们当前的工作流程,即使用 Frontpage Extensions 或 FTP 编辑网站的实时版本.并将其移动到更好的地方.在这种情况下,我设置为镜像实时服务器的开发服务器上的实时站点副本,删除首页扩展访问权限.然后设计师仍然可以拥有即时满足的相同效果,但我不必担心他们正在编辑实时文件.即使在 subversion 中使用共享用户/pass 仍然是版本控制.这可能并不理想,如果设计师实际上是程序员,我会尝试让他们完全参与进来,但事实并非如此.这是我在这种情况下能做的最好的事情,避免了巨大的学习曲线和停工.

I'm trying to take our current work flow, which is editing the LIVE version of a site using Frontpage Extensions or FTP. And move it to something BETTER. In this case a copy of the live site on a development server that I setup to mirror the live server, remove frontpage extensions access. Then the designers can still have the same effect of instant gratification but I will not have to worry they are editing the live files. Even using a shared user/pass in subversion is still version control. It may not be ideal and if the designers were actually programmers I would try to get them fully on board but that's just not the case. This is the best I can do in this case and avoid a huge learning curve and work stoppage.

推荐答案

根据我的经验,它开箱即用.在我的公司,我们已经使用这种设置多年并且没有遇到任何问题(除了共享工作副本的明显问题).

In my experience it will work just fine out of the box. At my company we have had this setup for a number of years and not experienced any problems (outside the obvious ones of having a shared working copy).

但是,如果您需要网站的实时"版本,您应该考虑使用单独的工作副本和触发器(挂钩)来更新提交时的共享位置.

You should however look into having separate working copies and a trigger (hook) that updates the shared location on commits if you need a "live" version of the site.

这篇关于你如何在 Subversion 中设置共享工作副本的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆