版本控制 - 从哪里开始？
我对此做了一些功课并了解版本控制的基本规则。我也环顾四周，没有发现任何真正可靠的东西，我明白很多。在我建议应该实施之后，我的任务是在我工作的公司建立版本控制。我们是一家Web开发公司，有许多同时运行的项目，因此我们需要进行版本控制。
唯一的问题是，我什至不知道从哪里开始。
我已将 Versions 应用程序下载到我的 Mac 上并了解如何使用该程序。我在桌面上创建了一个本地存储库，并向其中添加了一些文件，签出、提交、恢复以前的修订版等。就像我说的，我对版本控制的工作原理和功能有基本的了解，它只是设置对于我工作的公司来说这是主要问题。我想使用SVN，所以Win用户可以使用TortoiseSVN，Mac用户可以使用版本，所以我想使用的内容没有问题。它只是使用它。
我们在办公室连接了网络服务器，其中一台保存着我们所有的大量网络文件。我们还有实时网络服务器，其中所有文档都是实时的。
我是否在本地设置存储库？或者我应该在实时网络服务器上设置它吗？我不太确定该去哪里。我看着豆茎，但再次不知道该把它带到哪里。如果我必须自己运行一个回购协议，我会没事的。我有一个本地存储库，其中包含我的所有文件，或者在我使用过的一台旧机器上有一个存储库。
但我如何将其复制到我的办公环境中呢？我意识到版本控制的重要性。我们目前有诸如
- File.html
- File-BACKUP.html
- File-OLD.html
- File - Copy[2].html
等之
类的东西，这不是一个功能系统。
有人可以指导我详细了解如何设置并让实践在办公室有效运行吗？比如，一步一步或 SVN 傻瓜之类的。
我读过这里很多人链接到的 svn 书，但也不太理解它，只是让你知道，不要立即将我链接到那里！
谢谢。
I've done some homework on this and understand the basic rules of Version Control. I've also looked around on here and not found anything really solid that I understand much. I've been tasked with setting up version control at the company I work for after I suggested it should be implemented. We are a Web Development company with numerous simaltaneously running projects, hence we need to have version control.
Only thing is, I'm so stuck as to where to even begin with it.
I have downloaded Versions app onto my Mac and understand how to use the program. I've created a local repository on my desktop and have added some files to the it, checked out, committed, restored previous revisions, etc. Like I say, I have the basic understanding of how version control works and functions, it's just setting it up for the company I work for that is the major problem. I want to work with SVN, so Win users can use TortoiseSVN and Mac users can use Versions, so no problems on what I want to use. It's just using it.
We have web servers in the office that we connect to, one holds all of our numerous web files. We also have our live web server where all of our documents are live.
Do I set the repository up locally? Or do I set it up on the live web server? I'm not too sure where to go. I looked at beanstalk, but again, was clueless as to where I should be taking it. If I had to run a repo myself, I'd be fine. I'd have a local repo where all of my files were or have one on a old machine I have kicking about.
But how do I replicate that into my office environment? I am aware of the importance of the need for version control. We currently have things like
- File.html
- File-BACKUP.html
- File-OLD.html
- File - Copy[2].html
etc etc
Which isnt a functional system.
Could someone please direct me as to a good breakdown of how to set this up and get the practice running effectively in the office? Like, a step by step or SVN for dummies or whatever.
I've read the svn book that many people round here link to and don't understand it much more either, just so you're aware and don't just instantly link me through to there!
Thanks.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
因此，要抓住技术问题的核心；听起来您在设置 Subversion 服务器并让 TortoiseSVN/Versions 连接它时遇到困难？
为了使团队能够协同工作，您需要一个中央存储库。不要将其设置在本地计算机上 - 最好将其设置在专用网络上的新共享服务器上。如果您使用实时 Web 服务器来托管它，请确保使用 SSL 保护存储库。
我不会深入讨论如何设置中央服务器的具体细节，因为您已经说过您知道 Subversion 文档在哪里。如果您在这方面有任何具体问题，请随时在本网站上提出更多问题。然而，您确实要求提供有关设置的“傻瓜”教程：这里有一些适用于 Windows 和Linux。
为了让团队有效地使用它，我建议您首先将每个人聚集在一起并讨论其好处。除非每个人都参与并使用它，否则您不会成功。回答他们的任何问题，并确保你认真对待他们的任何担忧 - 离开并带着研究过的解决方案回来，不要只是告诉他们“颠覆的方式或高速公路”。我预计这将是您整个过程中最困难的挑战，但绝对值得坚持下去。
一旦设置完毕 - 通过在新项目中使用它（或导入非关键的现有项目）将其介绍给团队。保留一系列“如何做”提示（维基百科对此很有帮助），至少在团队的其他成员开始掌握基础知识之前是这样。最终，当其他人看到有用性时，您开始取得进展，此时您可以开始考虑将所有内容移植到 Subversion。
So to get to the nub of the technical problem; it sounds like you are having difficulty setting up a Subversion server and getting TortoiseSVN/Versions to connect with it?
For a team to work together, you need a central repository. DO NOT set it up on a local machine - ideally set it up on a new shared server on your private network. If you use the live Web server to host it instead, make sure the repository is secured using SSL.
I won't get into the gritty details on how to set up a central server, since you've already stated you know where the Subversion docs are. If you have any specific problems in this area, feel free to ask a few more questions on this site. You did, however, ask for a "dummies" tutorial on setting things up: Here are some for Windows and for Linux.
To get the team working effectively with it, I suggest you first get everyone together and discuss the benefits. You will not succeed unless everyone is on board and using it. Answer any questions they have, and make sure you take any concerns they have seriously - go away and come back with researched solutions, don't just tell them "Subversion's way or the highway". I expect this will be your most difficult challenge of the whole thing, but it is most certainly worthwhile persevering.
Once things are set up - introduce it to the team by using it with a new project (or import a non-critical existing one). Maintain a collection of "how to" tips (a Wiki is good for this), at least until the rest of the team start to grasp the basics. Eventually, you start to gain ground when the others see the usefulness, and at that point you can start considering porting everything to Subversion.
奇怪的是，这就像设置一个保管箱帐户并使用 Tortoise SVN 将本地 SVN 存储库放在您的保管箱文件夹中一样简单。
或者，您在服务器上设置了一个保管箱文件夹，然后相同的想法适用于多个用户。
进入保管箱文件夹后，只需创建一个文件夹，右键单击，然后执行 Tortoise SVN->;在这里创建存储库...
另请参阅 http ://thinkinging.com/2007/04/12/creating-a-local-subversion-repository-with-tortoisesvn/
Oddly enough, this can be as simple as setting up a drop-box account, and having your local SVN repository in your dropbox folder using Tortoise SVN.
Or you set up a dropbox folder on a server, and then the same idea applies but to multiple users.
Once you are in your dropbox folder, just make a folder, right click, and do Tortoise SVN-> Create Repository Here...
Also, see http://thinkinging.com/2007/04/12/creating-a-local-subversion-repository-with-tortoisesvn/
如果您想使用 svn（或其他集中式）版本控制系统，那么您应该创建可供用户 24x7 访问的存储库。如果存储库驻留在您自己的 PC 上，那么当您离线时其他用户将无法共享他们的更改。同样，您的用户不在办公室时是否需要提交或获取最新更改（这样本地办公室 PC 将不可用，但“实时”PC 可用）？
当然，如果你希望你的“实时网络服务器”向你的客户显示最新版本的文档，这样的“实时网络服务器”只是另一个 svn 客户端，你不应该将它与你的 svn 存储库混淆（这不会）这并不意味着它不能位于同一台 PC 上，只是“实时 Web 服务”不应该直接与您的存储库存储一起使用）。
或者，您可以考虑分布式版本控制系统，例如 git。
If you want to use svn (or other centralized) version control system, then you should create repository where it will be accessible to users 24x7. If the repository resides on your own PC, then other users will be unable to share their changes when you're offline. Similarly, will your users experience the need of commiting or getting the latest changes when they're not in the office (so that local office PC will not be available, but a "live" one will)?
Of course, if you want your "live web server" to show latest version of your documents to your customers, such a "live web server" is just another svn client, you should not mix it up with your svn repository (which doesn't mean it could not be on the same PC, it is just that "live web service" should not work with your repository storage directly).
Alternatively, you may consider distributed version control systems such as git.
如果您当前的问题是设置这些东西，那么您可以投入一些 Google 时间并为中央 SVN 服务器搜索现成的“设备”。有多种不同风格和不同附加组件，适用于 Windows 或 Linux。
使用其中之一还可以为你的同事提供更多的启动商誉，因为更多的东西开箱即用的机会更高。
If your current problem is setting up the stuff, then you could invest some Google-time and search for ready-to-use "appliances" for the central SVN server. There exists several in different flavours and different add-ons and either for Windows or Linux.
Using one of these may also provide some more startup-goodwill from you coworkers, because the chances are higher, that more stuff works just out of the box.
如果您的服务器是Windows，请下载并安装Visual svn服务器。 http://www.visualsvn.com/server/
管理工具将引导您完成存储库的设置，并为您提供访问它的 URL。通过电子邮件将该 URL 发送给您的团队，并让他们使用 Web 浏览器浏览该页面，他们将在其中验证其登录凭据。如果看起来不错，他们就可以将该 URL 粘贴到他们的 svn 客户端（例如 TortoiseSVN）中，然后就可以开始使用了。
If your server is windows, download and install visual svn server. http://www.visualsvn.com/server/
The admin tool will walk you through the setup of your repo, and will give you the URL to access it. E-mail that url to your team, and have them browse to the page with their web browser, where they will verify their login credentials. If that looks good, they can then paste the url into their svn client such as TortoiseSVN, and they're ready to roll.