在 Screwturn wiki 站点中创建 Mercurial 存储库是个好主意吗？
我有两个 ScrewTurn wiki 文档站点，用于我们的系统和用户文档。我的想法是在每个 wiki 站点根目录中创建一个 Mercurial 存储库。然后，每天安排一个流程添加新文件并将更改提交到存储库，并将更改集推送到备份存储库。
我意识到，默认情况下，ScrewTurn 会创建所有更改文件的副本，因此具有自己的更改跟踪，但我正在考虑关闭该行为。
我相信这会给我比默认行为和自动备份更好的版本控制。
我是否遗漏了一些注意事项？这是个好主意吗？一个坏主意？
I have two ScrewTurn wiki documentation sites that are used for our system and user documentation. My idea is to create a Mercurial repository in each wiki site root directory. Then on a daily basis have a scheduled process add new files and commit changes to the repository and push the changeset to a backup repository.
I realize that, by default, ScrewTurn creates copies of all changed files and therefore has its own change tracking but I am considering turning that behavior off.
I beleive this would give me better version control than the default behavior and an automated backup.
Are there some considerations that I am missing? Is this a good idea? A bad idea?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我对螺丝转动一无所知，但只要它的文件存储为文本并且您可以禁用修订跟踪，那么水银备份就是一个不错的选择。当然，您只能访问 cron 作业时存在的修订，但这也意味着您不会丢失超过 24 小时的编辑工作。
顺便说一句，mercurial 的主要作者 mpm 过去曾讨论过使用 DVCS 系统作为 wiki 系统的后端，但总体上并不赞成这个想法。如果我没记错的话，他的逻辑是，使用为一次仅更改一页的内容获取全局锁的数据存储没有多大意义。但是，这仅适用于您在每次更改后进行提交的情况；你每晚承诺的计划不存在这个问题。
另外，我是 rdiff-backup 的忠实粉丝，它以磁盘可浏览的方式执行节省空间的夜间快照。
I don't know anything about screwturn, but so long as its files are stored as text and you can disable revision tracking then mercurial backups are a fine option. You'll of course only have access to revisions that existed at the time of your cron job, but that also means you won't ever lose more than 24hs editing work.
Incidentally, mpm, mercurial's primary author, has talked about using DVCS systems as the backends for wiki systems in the past and was generally not-in-favor of the idea. If I recall correctly his logic was that using a datastore that acquires a global lock for something that's changed only a page at a time doesn't make much sense. However, that would only apply if you were committing after each change; your plan to commit nightly doesn't have that problem.
Alternately, I'm a big fan of rdiff-backup, which does space-efficient nightly snapshots in a disk-browsable manner.