推出网站更新的正确方法
我有一个注册网站，该网站会定期更新，并进行细微的更改。虽然这些“修复”不一定会带来任何问题，但我们正处于需要推出一些重大更改的阶段。
我正在寻找进行这些更改的正确方法，并指出，如果实时站点上出现“问题”，我需要尽快恢复到以前的“安全”状态。
我在网上搜索了一些关于“颠覆”的方法，但我有一些问题/问题：
1）我是否以正确的方式处理这个问题？
2）颠覆是正确的使用方法吗？
3）如果颠覆是一种方式，任何人都可以提供颠覆的“初学者指南”，因为我找到的大多数材料都假设您不仅对颠覆本身，而且对如何在 Linux 环境中实现都有广泛的了解。
值得注意的是：我在本地 Windows 计算机上运行所有代码，然后传递到运行 Cent OS 5 的媒体寺庙托管专用虚拟服务器。
I have an enrollment website which is updated on a fairly regular basis with minor changes. While these 'fixes' don't necessarily present any issue, we are in a phase where we need to roll out some major changes.
I am looking for the right way to make these changes, noting that if something goes "wrong" on the live-site, I need to revert back to a former 'safe' state as quickly as possible.
I have done some searching on the net about 'subversion' as a method to do just this but I have a few questions/issues:
1) Am I going about this the right way?
2) Is subversion the proper method to use?
3) If subversion is the way, can anybody provide a "beginner's guide" to subversion as most of the material I find assumes you have a vast understanding of, not only itself, but of how to implement within Linux environments as well.
of note: I run all my code on a local windows machine before passing over to a Media temple Hosted Dedicated Virtual server running Cent OS 5.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您不一定要使用 subversion 或任何版本控制系统才能恢复到安全更新。像 subversion 这样的工具很容易安装，并且非常适合对软件进行版本控制。但是，如果您只是希望能够恢复网站部署，有时最简单的方法是先备份服务器上的所有文件，然后应用更新。如果更新失败，只需恢复备份即可。您可以备份到临时目录、zip 文件等。Subversion
非常适合版本控制，但即使在非常小的/个人团队中，跟踪源代码更改也很有用，因为您可以在每次“提交”更改时应用注释进入版本控制系统。这些注释可以帮助您作为更改日志以供将来参考。此外，使用版本控制系统允许您比较单个文件的更改历史记录。即直观地看到单个文件的哪些部分从一个版本更改为下一个版本。这可以作为未来很好的参考。
如果您愿意，可以设置 Subversion 来跟踪源代码更改，但部署更改并能够在发生灾难时恢复的最实用方法是先备份所有网站文件。
这个 SVN 参考非常容易理解：http://svnbook.red-bean.com/
You don't have to necessarily use subversion, or any version control system, in order to revert back to your safe update. Tools like subversion are easy to install, and work great to version control your software. But, if you're just looking to simply be able to revert a website deployment, sometimes the easiest path is to simply back up all of your files on your server first, then apply your update. If the update fails, simply restore your backup. You can back up to temporary directories, zip files, etc.
Subversion is great for version control, but even on very small / individual teams it's useful to track your source code changes, since you can apply comments every time you "commit" your changes into the version control system. These comments can help to act as a change log for your future reference. In addition, using a version control system allows you to compare the change history of a single file. I.e. visually seeing what parts of a single file were changed from one version to the next. That can serve as a great future reference.
You could set up Subversion if you wanted to in order to track your source code changes, but the most pragmatic way to deploy your changes and be able to revert in the event of a disaster would be to simply back up all of your website files first.
This SVN reference is pretty easy to digest: http://svnbook.red-bean.com/