您将如何对个人数据（例如个人网站）使用版本控制？
这更多的是一个用例问题，但我使用 txt2tags 为个人网站生成静态文件。我正在考虑将这些信息存储在 git 存储库中。通常我使用 RCS，因为它最简单，而且我只是一个用户。
但人们似乎有很大的趋势使用 git/svn/cvs/etc。对于个人数据，我认为这也可能是至少学习该工具的一些基础知识的好方法。显然，大部分学习都是在协作环境中完成的。
回到问题：您将如何使用版本控制系统（例如 git）来管理个人网站？
This is more a use-case question, but I generate static files for a personal website using txt2tags. I was thinking of maybe storing this information in a git repository. Normally I use RCS since it's simplest, and I'm only a single user.
But there just seems to be a large trend of people using git/svn/cvs/etc. for personal data, and I thought this may also be a good way to at least learn some of the basics of the tool. Obviously most of the learning is done in an environment where you collaborate.
So back to the question: how would you use use a version control system such as git, to manage a personal website?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
在本地系统上创建一个存储库以包含文件的主副本。随时处理本地存储库中的网站并将网站部署到实时服务器目录。您可以使用现有工具来执行此操作，或者编写一个带有构建或导出例程和文件复制的小脚本。
最后一点是很好的做法，但并不是每个人都会这样做。有些人将存储库克隆的工作副本改为可通过 Web 访问。我不建议这样做 - Git 不会跟踪文件权限，您不应该直接在网站的实时副本上执行 VCS 操作，并且没有理由可能在 Web 上公开存储库的完整副本。
我使用 Webby 实用程序来构建我的网站，其中包括部署功能。 Capistrano 和 Fabric 是专门的部署工具。我知道 Capistrano 与您的 VCS 配合使用，使您能够轻松部署和回滚实时站点。
我还在另一个系统上克隆了我的存储库，我将更改推送到该系统 - 纯粹作为备份。
Create a repository on your local system to contain the master copy of your files. Work on the site in your local repository and deploy the Web site to the live server directory whenever. You could use an existing tool for this, or write a small script with a build or export routine and file copying.
The last bit is good practice, but not everybody does it. Some people make the working copy of a repository clone Web-accessible instead. I don't recommend this - Git doesn't track file permissions, you shouldn't be doing VCS operations directly on the live copy of your Web site, and there is no reason to potentially expose a complete copy of your repository on the Web.
I use the Webby utility to build my site, and this includes a deployment function. Capistrano and Fabric are specialized deployment tools. I know that Capistrano works with your VCS to enable you to easily deploy and rollback your live sites.
I also have a clone of my repository on another system, which I push changes to - purely as a backup.
我对所有数据进行版本控制。每次改变我都会承诺。
我的代码版本控制也允许备份。
I version all of my data. I commit each time I change it.
Versionning my code allow a backup too.
使用 git。 Git 为您提供了离线提交的便利以及将更改推送到其他机器的能力。我将配置文件（屏幕、shell、emacs...）保存在 git 中，以便它们在我的机器之间同步。还可以轻松地在您只是暂时使用的计算机上进行自定义设置。
将项目拆分到单独的存储库中（不要提交您的主文件夹），因为您只能使用 git 拉取整个存储库。
Use git. Git gives you the convenience of offline commits plus the ability to push changes to other machines. I keep my configuration files (screen, shell, emacs,...) in git to have them synchronized between my machines. Also makes it dead-easy to get your custom setup on a machine you're only temporarily using.
Split up projects into separate repositories (don't commit your home folder) as you can only pull whole repositories with git.
对于项目（甚至是非协作的），我使用 trunk/tags/branches 文件夹（我开始时没有使用，但经过艰苦的学习才知道），但对于个人文件，它们确实没有必要，特别是因为二进制文件无法合并。
在我满意的每组更改之后进行提交对我来说就足够了。
For projects (even non-collaborative) I use trunk/tags/branches folders (I didn't when I started but learnt the hard way) but for personal file they really aren't necessary, especially as binary files can't be merged.
A commit after every set of changes I'm comfortable with is good enough for me.