This document describes all of the available configuration options. The options are categorized by the lowest-level wikifier interface at which they are used. Some are required for the generation of a single page, others for the operation of a full wiki, and others yet for the operation of a wikiserver.

Configuration files

The primary method of configuration is to define options in a configuration file. All wikifier configuration files are written in the wikifier language:

@name:          MyWiki;      /home/www/mywiki;      []/pages;
@image.enable.pregeneration;        /* enable a boolean option */
-@page.enable.title;                /* disable a boolean option */

If you are using a wikiserver, you must have a dedicated configuration file for the server. This tells it where to listen and where to find the wikis you have configured on the server. This is typically called wikiserver.conf, and it is required as the first argument to the wikiserver executable.

Every wiki also requires its own configuration file. It may make sense to store your wiki configuration file at a path outside of the wiki root, just in case it contains sensitive information. If you are using a wikiserver, the path of each wiki's configuration file is defined in the server configuration using the[name].config option. If you are using Wikifier::Wiki directly, the path to the wiki configuration must be provided to the constructor:

my $wiki = Wikifier::Wiki->new(config_file => '/home/www/mywiki/wiki.conf');

Each wiki can optionally have a private configuration file. This is where the credentials of administrators can exist more securely than in the primary configuration. This file certainly should not be within the wiki root because that would probably allow anyone to download it from the web server. If you are using a wikiserver, the path of the private configuration is defined by[name].private. If you are using Wikifier::Wiki directly, the path to the private configuration may be provided to the constructor:

my $wiki = Wikifier::Wiki->new(
    config_file  => '/home/www/mywiki/wiki.conf',
    private_file => '/home/www/mywiki-private.conf',

Configuration directly from code

Another method of defining configuration values (rather than in a configuration file) is to do so directly from the code where you initialize the interface. This is probably only useful if you are using Wikifier::Page directly:

my $page = Wikifier::Page->new(
    file_path => $path,
    opts => {
        'name' => 'MyWiki',
        '' => '/wiki',
        '' => '/wiki/page'

Wikifier::Page options


Name of the wiki.

Default: Wiki


Option Description Default Wiki root '' (i.e. /) Page root /page
root.image Image root /images
root.file File root None

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 within the definitions of the rest:     /mywiki;     []/page;
@root.image:    []/images;

If you are using Wikifier::Wiki (or a wikiserver) in conjunction with image.enable.cache and image.enable.pregeneration, you should set root.image to wherever your cache directory can be found on the HTTP root. This is where generated images are cached, and full-sized images are symbolically linked to. This allows the web server to deliver images directly, which is certainly most efficient.

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


Option Description
dir.wikifier wikifier repository Wiki root directory Page files stored here
dir.image Image originals stored here
dir.model Model files stored here Markdown files stored here
dir.cache Generated content and metadata stored here

Directories on the filesystem. It is strongly recommended that they are absolute paths; otherwise they will be dictated by whichever directory the script is started from. All are required except dir.wikifier and

It is recommended that all of the files related to one wiki exist within a master wiki directory (, but this is not technically required unless you are using Wikifer::Wiki's built-in revision tracking.      /home/www/mywiki;      []/pages;
@dir.cache:     []/cache;

dir.wikifier can be inferred from server.dir.wikifier if you are using a wikiserver with this directive set.


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.

Option Description Default
external.[wiki_id].name External wiki name, displayed in link tooltips
external.[wiki_id].root External wiki page root
external.[wiki_id].type External wiki type wikifier

Accepted values for type

  • wikifier (this is default)

  • mediawiki

  • none (URI encode only)

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

@external.wp: {
    name: Wikipedia;
    type: mediawiki;

From the page source, this looks like:

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


If enabled, the first section's title will be the title of the page. You may want to disable this if your wiki content is embedded within a template that has its own place for the page title.

Default: Enabled


The method which the wikifier should use to scale images.

Accepted values

  • javascript - JavaScript-injected image sizing

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

When set to server, the options image.calc and image.sizer are required. If using Wikifier::Page directly, image.calc is provided but requires that you install Image::Size. In that case, you are required to provide a custom image.sizer routine. If using Wikifier::Wiki, image.calc and image.sizer are both provided, but GD must be installed from the CPAN.

Default (Page): javascript

Default (Wiki): server


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

Returns (scaled width, scaled height, full width, full height, fullsize). fullsize is true if the scaled dimensions are equal to the full-sized dimensions.

Default (Page): built in, uses Image::Size

Default (Wiki): built in, uses GD


The desired rounding method used when determining image dimensions. Used by the default image.calc. If a custom image.calc is provided, this will not be utilized.

Accepted values

  • normal - round up from .5 or more, down for less

  • up - always round up

  • down - always round down

Default: normal


A code 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.

If using image.size_method server, image.sizer must be provided (unless using Wikifier::Wiki, which provides its own).

Returns a URL.

Default (Page): none; custom code required

Default (Wiki): built in

Wikifier::Wiki public options


The desired file type for generated images. This is used by Wikifier::Wiki when generating images of different dimensions. All resulting images will be in this format, regardless of their original format.

Accepted values

  • png - larger, lossless compression

  • jpeg - smaller, lossy compression

Default: png


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

Default: 100


Enable retina display support. Wikifier::Wiki will interpret and properly handle @2x or larger scaled versions of images.

The value of this option is the max scale to support; e.g.

@image.enable.retina: 3;

to support both @2x and @3x scaling.

Default: 3


Enable pregeneration of images. Images will be generated as pages that require them are generated. This contrasts from the default behavior in which images are generated as they are requested.

The advantage of this option is that it allows images to be served directly by a web server without summoning any wikifier software, decreasing the page load time.

The disadvantage is slower page generation time if new images have been added since the last generation time.

Requires: image.enable.cache

Default: Enabled


If enabled, Wikifier::Wiki will create page categories that track image usage. This is particularly useful for a Wikifier::Server feature that allows images and pages to be generated as they are modified.

Default: Enabled


If enabled, Wikifier::Wiki will only generate images in dimensions used by pages on the wiki. This prevents useless resource usage and abuse.

Default: Enabled


Enable caching of generated images.

Required by: image.enable.pregeneration, image.enable.restriction

Default: Enabled


Enable caching of generated pages.

Default: Enabled


Number of pages to display on a single category posts page.

Default: 5


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:


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 be preferred.

Default: None; show newest at top


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

You can also set the title of a category from within the category file itself using the "title" key.

Default: None; page filename displayed as title


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): MyWiki;

Example (on main page):

Welcome to [@site.display_name]!

Wikifier::Wiki extended options

These options are not used by Wikifier::Wiki directly, but may be required by frontends or admin panels. They are documented here for consistency across software built atop wikifier.


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



If enabled, the wiki root will redirect to the main page rather than just displaying it at the root location.


@error_page: some_page;

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


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

@navigation: map {
    Main page: /page/welcome;
    Rules: /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: map {
    Home: /page/welcome;
    About: map {
        Company info: /page/our_company;
    Contact: /contact;


Name or path of the template used by the wiki.

@template: default;

Filename for the wiki logo, relative to dir.image.

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

@logo: logo.png;

Wikifier::Wiki private options

Private Wikifier::Wiki options may be in a separation configuration file. This is where administrator credentials are stored. You can also put them in the primary configuration file, but this is not recommended.


The real name for the administrator [username]. This is used to attribute page creation, image upload, etc. to the user. It may be displayed to the public as the author or maintainer of a page or the owner of some file. It is also used for Wikifier::Wiki's built-in revision tracking.


The email address of the administrator [username]. Currently this is used only for Wikifier::Wiki's built-in revision tracking.


The type of encryption used for the password of administrator [username].

Accepted values

  • none (plain text)

  • sha1

  • sha256

  • sha512

Default: sha1


The password of the administrator [username]. It must be encrypted in the crypt set by admin.[username].crypt.

Wikifier::Server options


Path to the wikifier repository. This is optional but strongly recommended. Specifying it here is preferred over the dir.wikifier wiki option.

Path to some directory where wikis are stored. Your wikis do not all have to be in the same directory, so this is optional. But if you do choose to do it that way, this is used to infer and[name].config.


The path of a UNIX socket to listen on.

If unspecified, the server will not listen on a UNIX socket.


If enabled, the Wikifier::Server will generate all pages upon the first start. It will then monitor all page files and regenerate them as soon as they are modified, greatly reducing the first page load time.

Requires: page.enable.cache

Default: Disabled (but strongly recommended)[name].enable

Enables the wiki by the name of [name]. Any wikis configured that do not have this option present will be skipped. Any number of wikis can be configured on a single server using this.[name].config

The path to the configuration file for the wiki by the name of [name]. This is required for each wiki unless is set.


The path to the PRIVATE configuration file for the wiki by the name of [name]. This is where administrator credentials are stored. If it is not provided, it will be assumed that this information is in the primary configuration file. Be sure that the private configuration is not inside the HTTP server root or has proper permissions to deny access to it.[name].password

The read authentication password for the wiki by the name of [name] in plain text. This is required unless the wikiserver is reached via standard I/O (such as with the default quiki configuration).