A small Rails engine that provides an opinionated, git-based, Markdown wiki.

This has been abstracted from a proprietary tool, and so is not well documented and lacks a standalone test suite.

This aims to become a suitable replacement for GollumRails, which does not actually use gollum-lib, but also provides an engine with Gollum-like features. (The name is historic.)

If instead of a mountable engine you want to use gollum-lib to weave wiki functionality into your own models and views, consider gollum_rails. If you just want a wiki that uses your existing database, look at Irwi

Rails Wiki exists because we desired a git-backed wiki using Markdown, YAML frontmatter, and a hierarchical namespace for pages and attachments.

Rails Wiki is based on gollum-lib. None of Gollum's layout (e.g. sidebars, headers, footers) are implemented, and most of the text filters (e.g. macros, code, diagrams) have been disabled. Also unlike Gollum, the hierarchy of pages is considered meaningful.

The storage structure will be familiar to users of Middleman or Jekyll. Each page is an .md file with YAML frontmatter for metadata. Other files are treated as attachments to the page associated with their containing directory.

All storage is via a local Git repository. Optionally, a remote can be specified and changes will be pushed to it.

Optionally, a rather blunt attempt is made to pull/push changes to an upstream repository.

Add rails-wiki to your Gemfile

gem 'rails-wiki'

Your application controller needs to provide two methods:

• auth_required is called on every request
• current_user returns a user object

The user object must response to .name and .email with string values.

You will probably wish to override the sparse view layout. Create a layouts/wiki (e.g. at app/views/layouts/wiki.html.erb) within your app, using the content blocks seen in the default layout.

Until gollum-lib#180 is resolved there is a hardcoded but unnecessary dependency on grit in gollum-lib. This in turn requires charlock_holmes, which can be problematic.

To avoid this, you may use our temporary fork of gollum-lib by including it in your Gemfile prior to rails-wiki:

gem 'gollum-lib', git: 'https://github.com/TheArtificial/gollum-lib.git', branch: 'master'

(This discussion may be interesting if you're curious about this approach to a temporary issue.)

In your routes.rb, specify a mount point:

mount Wiki::Engine, at: '/wiki'

In your config/environment/* files, configure the wiki:

require 'rails-wiki'
Wiki.local_directory = 'db/wiki'

While not recommended, upstream sync can be provided by setting additional properties on the module:

Wiki.remote_url = "https://github.com/TheArtificial/wiki"
Wiki.history_url = "https://github.com/TheArtificial/wiki/commits/master/"

TODO: move this configuration to an initializer?

See the test/dummy app for an example.

Pathnames that begin with underscore (_) are reserved.

1. Markdown link rooting
2. Recursive page deletion
3. Individual attachment deletion
4. Path redirection rules
5. Configurable help paths
6. Nicer attachment upload
7. Nicer page editing