Configuration

name

Name of the wiki.

Default: Wiki

host.wiki

Hostname for the wiki.

It may be overridden in the server configuration by server.wiki.[name].host.

If specified in neither place, the wiki is accessible from all available hosts.

Default: None (all hosts)

dir.wiki

Path to the wiki.

With webserver, this can be omitted if either:

1. server.dir.wiki is configured, and the wiki is located in that directory.
2. server.wiki.[name].dir is configured.

In all other cases, it is Required.

Default (webserver): server.dir.wiki/[name]

root

Optional. HTTP roots. These are relative to the server HTTP root, NOT the wiki root. They are used for link targets and image URLs; they will never be used to locate content on the filesystem. Do not include trailing slashes.

It may be useful to use root.wiki within the definitions of the rest:

@root.wiki:     /mywiki;
@root.page:     [@root.wiki]/page;
@root.image:    [@root.wiki]/images;

If you specify root.file, the entire wiki directory (as specified by dir.wiki) will be indexed by the web server at this path. Note that this will likely expose your wiki configuration.

external

Optional. External wiki information.

You can configure any number of external wikis, each referred to by a shorthand identifier [wiki_id] consisting of word-like characters.

Accepted values for type

• quiki (this is default)
• mediawiki
• none (URI encode only)

The default configuration includes the wp identifier for the English Wikipedia:

@external.wp: {
    name: Wikipedia;  /* appears in tooltip */
    root: http://en.wikipedia.org/wiki;
    type: mediawiki;
};

From the page source, this looks like:

[[ Cats | wp: Cat ]] are a type of [[ wp: animal ]].

page.enable.title

Optional. If enabled, the first section's heading defaults to the title of the page, and all other headings on the page are sized down one.

You may want to disable this at the wiki level if your wiki content is embedded within a template that has its own place for the page title:

[email protected];

Default: Enabled

image.size_method

Optional. The method which quiki should use to scale images.

This is here for purposes of documentation only; there's probably no reason to ever stray away from the default for whichever quiki interface is used.

Accepted values

• javascript - JavaScript-injected image sizing
• server - server-side image sizing using image.sizer and image.calc (recommended)

Default (webserver): server

Default (low-level): javascript

image.calc

Optional. A function reference that calculates a missing dimension of an image. This is utilized only when image.size_method is server.

This is here for purposes of documentation only and can only be configured using quiki's wikifier engine API directly.

Default: (webserver) built-in function

image.sizer

Optional. A function reference that returns the URL to a sized version of an image. After using image.calc to find the dimensions of an image, image.sizer is called to generate a URL for the image at those dimensions.

This is here for purposes of documentation only and can only be configured using quiki's wikifier engine API directly.

Default: (webserver) built-in function

image.type

Optional. The desired file type for generated images.

When configured, all resulting images will be in this format, regardless of their original format. Unless you have a specific reason to do this, omit this option to preserve original image formats.

Accepted values

• png - larger, lossless compression
• jpeg - smaller, lossy compression

Default: none (preserve original format)

image.quality

Optional. The desired quality of generated images with lossy compression. This is only utilized if image.type is set to jpeg.

Default: 100

image.retina

Optional. Image scales to enable for displays with a greater than 1:1 pixel ratio.

For instance, to support both @2x and @3x scaling:

@image.retina: 2, 3;

Default: 2, 3

page.enable.cache

Optional. Enable caching of generated pages.

For best performance, page caching is enabled by default, and quiki will only generate pages if the source file has been modified since the cache file was last written.

Default: Enabled

cat.per_page

Optional. Maximum number of pages to display on a single category posts page.

Default: 5

cat.[name].main

Optional. Set the main page for the category by the name of [name]. This means that it will be displayed before all other categories, regardless of their creation dates. The value of this option is the page filename.

You can also mark a page as the main page of a category from within the page source itself, like so:

@category.some_cat.main;

If multiple pages are marked as the main page of a category, the one with the most recent creation time is preferred. If this option is provided, however, the page specified by it will always take precedence.

Default: none (show newest first)

cat.[name].title

Optional. Sets the human-readable title for the category by the name of [name].

Default: none

var.*

Optional. Global wiki variable space. Variables defined in this space will be available throughout the wiki. However they may be overwritten on a particular page.

Example (in config):

@var.site.url: http://mywiki.example.com;
@var.site.display_name: MyWiki;

Example (on main page):

Welcome to [@site.display_name]!

main_page

Optional. Name of the main page.

This should not be the page's title but rather a filename, relative to the wiki page directory. The extension is not necessary.

@main_page: Welcome Page; /* normalized to welcome_page.page */

Default (webserver): None

main_redirect

Optional. If enabled, the wiki root redirects to the main page rather than just rendering it at the root location.

@main_redirect;

Default (webserver): Disabled

error_page

Optional. Name of the error page.

This should not be the page's title but rather a filename, relative to the wiki page directory. The extension is not necessary.

@error_page: Error; /* normalized to error.page */

Default (webserver): None (show generic error text)

navigation

Optional. Navigation items.

Keys are unformatted text to be displayed, with spaces permitted. Values are URLs, relative to the current page (NOT the wiki root).

It is good practice to refer to root:

@navigation: {
    Main page:  [@root.page]/welcome_page;
    Rules:      [@root.page]/rules;
};

You can nest maps to create sublists at any level, but the number of levels supported depends on the frontend or template being used by the wiki.

@navigation: {
    Home: /page/welcome;
    About: {
        Company info: /page/our_company;
        Facebook: http://facebook.com/our.company;
    };
    Contact: /contact;
};

Default (webserver): None

template

Optional. Name or path of the template used by the wiki.

@template: default;

Default (webserver): default

logo

Optional. Filename for the wiki logo, relative to the wiki image directory.

Frontends like webserver automatically generate the logo in whatever dimensions are needed and display it where appropriate.

@logo: logo.png;

server.dir.wiki

Optional. Path to some directory where wikis are stored.

Your wikis do not all have to be in the same directory, so this is optional. However, if you make use of this, quiki can infer dir.wiki for each wiki, allowing you to omit the server.wiki.[name].dir options.

server.dir.adminifier

Optional (Required with adminifier.enable). Path to adminifier resources.

server.enable.pregeneration

Optional. If enabled, webserver pre-generates all pages and images upon start.

Requires: page.enable.cache

Default: Enabled

server.enable.monitor

Optional. If enabled, webserver uses operating system facilities to monitor wiki directories and pre-generate content when the source files are changed.

Requires: page.enable.cache

Default: Enabled

server.http.port

Required. Port for HTTP server to listen on.

server.http.port: 8080;

You can also say unix to listen on a UNIX socket.

server.http.bind

Optional. Host to bind to.

@server.http.bind: 127.0.0.1;

Or, you can listen on a UNIX socket:

@server.http.port:  unix;
@server.http.bind:  /var/run/quiki.sock;

Default: none (bind to all available hosts)

server.dir.template

Optional. Template search paths.

@server.dir.template: /home/www/wiki-templates;

This is a comma-separated list of paths to look for templates when they are specified by name in the wiki configuration. If you're running multiple wikis that share a template, or if you are using the default template, this optional is useful. Otherwise, you can just specify the absolute path to each wiki's template in the template directive.

server.wiki.[name].enable

Optional. Enable the wiki with shortname [name].

Any wikis configured that do not have this option present are skipped. Any number of wikis can be configured on a single server using this.

server.wiki.[name].dir

Optional. Path to the wiki with shortname [name].

This can be omitted if server.dir.wiki is set and the wiki is located within that container. The shortname becomes the name of its directory inside server.dir.wiki.

Default: server.dir.wiki/[name]

adminifier.enable

Optional. Enables the adminifier server administration panel.

Requires: server.dir.adminifier Default: Disabled (but enabled in the example configuration)

adminifier.host

Optional. Specifies an HTTP host to bind to for the adminifier web panel.

Default: None (i.e., adminifier is available on all hosts)

adminifier.root

Optional. Specifies the HTTP root for the adminifier web panel.

If adminifier.host is specified and that hostname is dedicated to adminifier, you can set adminifier.root empty to occupy the entire host, for example:

@adminifier.host: admin.mywiki.example.com;
@adminifier.root: ;

Default: None (i.e., /)