I've actually had good success with a Wiki. Use something where you can control logins easily — Mediawiki is okay, but requires some PHP hacking — and build some templates for processes, inventories, and so forth.
Update
Actually, I must have needed coffee. Trac is pretty nearly ideal; better access control, integrated issue tracking, and a somewhat stronger text model. You can even tie it directly to your subversion repository so that you can hook actual scripts to their runbook pages.
Wikis are indeed a good approach. You can set up sharepoint for that and get nice features like update history, links that always point to current information and such.
If you use something like Puppet, (or Chef, or CFEngine, etc.) to build and manage your machines, then most of the runbook contents can live inside the puppet config, leaving you with a lot less stuff (just the location and password for the puppetmaster, if you take it to extremes!) to put in your wiki.
发布评论
评论（3）
事实上，我在 Wiki 方面取得了巨大成功。 使用可以轻松控制登录的东西 - Mediawiki 还可以，但需要一些 PHP 黑客技术 - 并为流程、库存等构建一些模板。
更新
事实上，我一定需要咖啡。 Trac 几乎是理想的； 更好的访问控制、集成的问题跟踪以及更强大的文本模型。 您甚至可以将其直接绑定到您的 subversion 存储库，以便您可以将实际脚本挂接到其 Runbook 页面。
I've actually had good success with a Wiki. Use something where you can control logins easily — Mediawiki is okay, but requires some PHP hacking — and build some templates for processes, inventories, and so forth.
Update
Actually, I must have needed coffee. Trac is pretty nearly ideal; better access control, integrated issue tracking, and a somewhat stronger text model. You can even tie it directly to your subversion repository so that you can hook actual scripts to their runbook pages.
维基确实是一个很好的方法。 您可以为此设置共享点并获得一些不错的功能，例如更新历史记录、始终指向当前信息的链接等。
Wikis are indeed a good approach. You can set up sharepoint for that and get nice features like update history, links that always point to current information and such.
如果您使用类似 Puppet（或 Chef、或 CFEngine 等）来构建和管理如果你的机器上有，那么大部分 Runbook 内容都可以存在于 puppet 配置中，这样你就可以在 wiki 中放入更少的内容（只有 puppetmaster 的位置和密码，如果你采取极端的话！）。
If you use something like Puppet, (or Chef, or CFEngine, etc.) to build and manage your machines, then most of the runbook contents can live inside the puppet config, leaving you with a lot less stuff (just the location and password for the puppetmaster, if you take it to extremes!) to put in your wiki.