基于Git的内容管理？ [英] Git-based content management?
问题描述
我在寻找可以提供和编辑位于Git存储库中的内容的Ruby CMS（或插件）。我不喜欢我的内容在一个数据库。用户，设置，评论，罚款。但没有更多的内容。
I'm looking for a Ruby CMS (or plugin) that can serve and edit content located in a Git repository. I'm sick of having my content in a db. Users, settings, comments, fine. But no more content.
每个实时编辑页面都需要自动，立即提交以防止服务器端合并。此外，无论何时推送新的更改，都需要立即在文件系统上更新。
Each live edit to a page will need to be automatically, immediately committed to prevent the need for server-side merging. Also, whenever new changes are pushed, they will need to be immediately updated on the filesystem.
Refinery CMS文档似乎做了类似的工作，
Refinery CMS documentation seems to do something similar, although perhaps with a remote repository.
我已经阅读了关于GitModel和git-blog，但我仍然在寻找一些符合我需要的东西。
I've read about GitModel and git-blog, but I'm still looking for something that matches my needs a bit closer.
编辑：我的偏见内容数据库仅适用于需要高度自定义的网站，并且不能使用任何CMS。
其代码与其内容一样发展的网站。这是在DB中有内容是一个完全的噩梦。当您需要同时分叉内容和代码时，他们将它们合并到后面的生产。数据库不分支和合并。
我有这样的网站。
仅支持DB的内容的性能参数为null。我在5年前写了一个CMS，它从文件系统同步数据库，其中文件系统始终是主副本。它轻松扩展到100,000页，维持10ms响应时间和2s重建索引时间。所有内容，元数据，标签，日期等的完全可搜索的索引。heck，我写在它在地球上最慢，最痛苦的框架，ASP.NET。实际上，它几乎使ASP.NET可以承受，它已经为各种公司服务非常好，因为他们有同样的网站，如上所述。
The performance argument in favor of DB-only content is null and void. I wrote a CMS 5 years ago that synchronizes the database from the filesystem, where the filesystem is always the master copy. It scaled easily to 100,000 pages, maintaining 10ms response times and 2s reindex times. Fully searchable indexes of all the content, metadata, tags, dates, etc. And heck, I wrote it in the slowest, most painful framework on the planet, ASP.NET. It actually almost made ASP.NET bearable, and it has served various companies extremely well, since they had the same kind of site as mentioned above.
小型网站可以直接使用内存中缓存，完全跳过数据库内容
仅数据库内容的有效参数是编辑的可扩展性。编辑者必须使用相同的服务器，尽管更改可以向外复制。但是在快速变化的，高度定制的网站，它们像内容一样频繁地改变代码，分布式/社区编辑所述代码和内容是不太可能的。
社区/分布式编辑可以使用不同的系统。
A valid argument for db-only content is scalability of editing. Editors must all use the same server, although changes can be replicated outward. But in the case of quick-changing, highly customized sites who change code as often as content, distributed/community editing of said code and content is unlikely. Community/distributed editing can use a different system.
到目前为止，我最亲近的是使用Cloud9编辑git存储库（Nesta CMS），然后通过命令行推送更改。它很慢，但至少它是基于网络的情况下，我的dev机器不方便，我发现我拼错了我的名字在一篇文章。仍在寻找更好的选择。
So far, the closest I have come is using Cloud9 to edit a git repository of content (Nesta CMS), then push the changes via the command line. It's slow, but at least it's web-based in case my dev machine isn't handy which I discover I misspelled my name in an article. Still looking for better options.
推荐答案
我最终实施了一个 micro-CMS名为Hardwired 一个出色的工作，留在我的方式。
I ended up implementing a micro-CMS called Hardwired that does an excellent job of staying out of my way.
试试。
这篇关于基于Git的内容管理？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
