Sophie

Sophie

distrib > Mageia > 7 > armv7hl > media > core-release > by-pkgid > d8544620e4ac7bee48ddb48c85d55709 > files > 600

ikiwiki-3.20190228-1.mga7.noarch.rpm

<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>

<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>usage</title>
<meta name="viewport" content="width=device-width, initial-scale=1" />

<link rel="stylesheet" href="style.css" type="text/css" />

<link rel="stylesheet" href="local.css" type="text/css" />










</head>
<body>

<div class="page">

<div class="pageheader">
<div class="header">
<span>
<span class="parentlinks">

<a href="./index.html">ikiwiki</a>/ 

</span>
<span class="title">
usage

</span>
</span>



</div>









</div>





<div id="pagebody">

<div id="content" role="main">
<h1>NAME</h1>

<p>ikiwiki - a wiki compiler</p>

<h1>SYNOPSIS</h1>

<p>ikiwiki [options] source destination</p>

<p>ikiwiki --setup setupfile [options]</p>

<h1>DESCRIPTION</h1>

<p><code>ikiwiki</code> is a wiki compiler. It builds static HTML pages for a wiki, from
<code>source</code> in the <a href="./ikiwiki/markdown.html">Markdown</a> language (or others), and writes it out to
<code>destination</code>.</p>

<p>Note that most options can be shortened to single letters, boolean
flags such as --verbose can be negated with --no-verbose, and
options such as --verbose can also be spelled like -verbose.</p>

<h1>MODE OPTIONS</h1>

<p>These options control the mode that ikiwiki operates in.</p>

<ul>
<li><p>--refresh</p>

<p>Refresh the wiki, updating any changed pages. This is the default
behavior if no other mode action is specified (but note that --setup is
a mode action, and has different default behavior).</p></li>
<li><p>--rebuild</p>

<p>Force a rebuild of all pages.</p></li>
<li><p>--setup setupfile</p>

<p>Load options from the given setup file. If no other mode action is specified,
generate wrappers and rebuild the wiki, as if --rebuild --wrappers were used.
If you only want to build any changed pages, you can use --refresh with
--setup.</p></li>
<li><p>--changesetup setupfile</p>

<p>Reads the setup file, adds any configuration changes specified by other
options, and writes the new configuration back to the setup file. Also
updates any configured wrappers. In this mode, the wiki is not fully
rebuilt, unless you also add --rebuild.</p>

<p>Example, to enable some plugins:</p>

<p>ikiwiki --changesetup ~/ikiwiki.setup --plugin goodstuff --plugin calendar</p></li>
<li><p>--dumpsetup setupfile</p>

<p>Causes ikiwiki to write to the specified setup file, dumping out
its current configuration.</p></li>
<li><p>--wrappers</p>

<p>If used with --setup --refresh, this makes it also update any configured
wrappers.</p></li>
<li><p>--clean</p>

<p>This makes ikiwiki clean up by removing any files it generated in the
<code>destination</code> directory, as well as any configured wrappers, and the
<code>.ikiwiki</code> state directory. This is mostly useful if you're running
ikiwiki in a Makefile to build documentation and want a corresponding
<code>clean</code> target.</p></li>
<li><p>--cgi</p>

<p>Enable <a href="./cgi.html">CGI</a> mode. In cgi mode ikiwiki runs as a cgi script, and
supports editing pages, signing in, and registration.</p>

<p>To use ikiwiki as a <a href="./cgi.html">CGI</a> program you need to use --wrapper or --setup
to generate a wrapper. The wrapper will generally need to run suid 6755 to
the user who owns the <code>source</code> and <code>destination</code> directories.</p></li>
<li><p>--wrapper [file]</p>

<p>Generate a wrapper binary that is hardcoded to do action specified by
the other options, using the specified input files and <code>destination</code>
directory. The filename to use for the wrapper is optional.</p>

<p>The wrapper is designed to be safely made suid and be run by untrusted
users, as a <a href="./post-commit.html">post-commit</a> hook, or as a <a href="./cgi.html">CGI</a>.</p>

<p>Note that the generated wrapper will ignore all command line parameters.</p></li>
<li><p>--aggregate</p>

<p>If the <a href="./plugins/aggregate.html">aggregate</a> plugin is enabled, this makes ikiwiki poll
configured feeds and save new posts to the srcdir.</p>

<p>Note that to rebuild previously aggregated posts, use the --rebuild option
along with this one. --rebuild will also force feeds to be polled even if
they were polled recently.</p></li>
<li><p>--render file</p>

<p>Renders a single file, outputting the resulting html. Does not save state,
so this cannot be used for building whole wikis, but it is useful for
previewing an edited file at the command line. Generally used in conjunction
with --setup to load in a wiki's setup:</p>

<p>ikiwiki --setup ~/ikiwiki.setup --render foo.mdwn</p></li>
<li><p>--post-commit</p>

<p>Run in post-commit mode, the same as if called by a <a href="./post-commit.html">post-commit</a> hook.
This is probably only useful when using ikiwiki with a web server on one host
and a repository on another, to allow the repository's real post-commit
hook to ssh to the web server host and manually run ikiwiki to update
the web site.</p></li>
<li><p>--version</p>

<p>Print ikiwiki's version number.</p></li>
</ul>

<h1>CONFIG OPTIONS</h1>

<p>These options configure the wiki. Note that <a href="./plugins.html">plugins</a> can add additional
configuration options of their own. All of these options and more besides can
also be configured using a setup file.</p>

<ul>
<li><p>--wikiname name</p>

<p>The name of the wiki, default is "wiki".</p></li>
<li><p>--templatedir dir</p>

<p>Specify the directory that <a href="./templates.html">templates</a> are stored in.
Default is <code>/usr/share/ikiwiki/templates</code>, or another location as configured at
build time. If the templatedir is changed, missing templates will still
be searched for in the default location as a fallback. Templates can also be
placed in the "templates/" subdirectory of the srcdir.</p>

<p>Note that if you choose to copy and modify ikiwiki's templates, you will need
to be careful to keep them up to date when upgrading to new versions of
ikiwiki. Old versions of templates do not always work with new ikiwiki
versions.</p></li>
<li><p>--underlaydir dir</p>

<p>Specify the directory that is used to underlay the source directory.
Source files will be taken from here unless overridden by a file in the
source directory. Default is <code>/usr/share/ikiwiki/basewiki</code> or another
location as configured at build time.</p></li>
<li><p>--wrappermode mode</p>

<p>Specify a mode to chmod the wrapper to after creating it.</p></li>
<li><p>--wrappergroup group</p>

<p>Specify what unix group the wrapper should be owned by. This can be
useful if the wrapper needs to be owned by a group other than the default.
For example, if a project has a repository with multiple committers with
access controlled by a group, it makes sense for the ikiwiki wrappers
to run setgid to that group.</p></li>
<li><p>--rcs=svn|git|.., --no-rcs</p>

<p>Enable or disable use of a <a href="./rcs.html">revision control system</a>.</p>

<p>The <code>source</code> directory will be assumed to be a working copy, or clone, or
whatever the revision control system you select uses.</p>

<p>In <a href="./cgi.html">CGI</a> mode, with a revision control system enabled, pages edited via
the web will be committed.</p>

<p>No revision control is enabled by default.</p></li>
<li><p>--svnrepo /svn/wiki</p>

<p>Specify the location of the svn repository for the wiki.</p></li>
<li><p>--svnpath trunk</p>

<p>Specify the path inside your svn repository where the wiki is located.
This defaults to <code>trunk</code>; change it if your wiki is at some other path
inside the repository. If your wiki is rooted at the top of the repository,
set svnpath to "".</p></li>
<li><p>--rss, --norss</p>

<p>If rss is set, ikiwiki will default to generating RSS feeds for pages
that inline a <a href="./blog.html">blog</a>.</p></li>
<li><p>--allowrss</p>

<p>If allowrss is set, and rss is not set, ikiwiki will not default to
generating RSS feeds, but setting <code>rss=yes</code> in the inline directive can
override this default and generate a feed.</p></li>
<li><p>--atom, --noatom</p>

<p>If atom is set, ikiwiki will default to generating Atom feeds for pages
that inline a <a href="./blog.html">blog</a>.</p></li>
<li><p>--allowatom</p>

<p>If allowatom is set, and rss is not set, ikiwiki will not default to
generating Atom feeds, but setting <code>atom=yes</code> in the inline directive can
override this default and generate a feed.</p></li>
<li><p>--pingurl URL</p>

<p>Set this to the URL of an XML-RPC service to ping when an RSS feed is
updated. For example, to ping Technorati, use the URL
http://rpc.technorati.com/rpc/ping</p>

<p>This parameter can be specified multiple times to specify more than one
URL to ping.</p></li>
<li><p>--url URL</p>

<p>Specifies the URL to the wiki. This is a required parameter in <a href="./cgi.html">CGI</a> mode.</p></li>
<li><p>--cgiurl http://example.org/ikiwiki.cgi</p>

<p>Specifies the URL to the ikiwiki <a href="./cgi.html">CGI</a> script wrapper. Required when
building the wiki for links to the cgi script to be generated.</p></li>
<li><p>--historyurl URL</p>

<p>Specifies the URL to link to for page history browsing. In the URL,
"[[file]]" is replaced with the file to browse. It's common to use
<span class="createlink">ViewVC</span> for this.</p></li>
<li><p>--adminemail you@example.org</p>

<p>Specifies the email address that ikiwiki should use for sending email.</p></li>
<li><p>--diffurl URL</p>

<p>Specifies the URL to link to for a diff of changes to a page. In the URL,
"[[file]]" is replaced with the file to browse, "[[r1]]" is the old
revision of the page, and "[[r2]]" is the new revision. It's common to use
<span class="createlink">ViewVC</span> for this.</p></li>
<li><p>--exclude regexp</p>

<p>Specifies a rexexp of source files to exclude from processing.
May be specified multiple times to add to exclude list.</p></li>
<li><p>--include regexp</p>

<p>Specifies a rexexp of source files, that would normally be excluded,
but that you wish to include in processing.
May be specified multiple times to add to include list.</p></li>
<li><p>--adminuser name</p>

<p>Specifies a username of a user (or, if openid is enabled, an openid) 
who has the powers of a wiki admin. Currently allows locking of any page,
and <span class="createlink">banning</span> users, as well as powers granted by
enabled plugins (such as <a href="./plugins/moderatedcomments.html">moderating comments</a> 
and <a href="./plugins/websetup.html">websetup</a>. May be specified multiple times for multiple
admins.</p>

<p>For an openid user specify the full URL of the login, including "http://".</p></li>
<li><p>--plugin name</p>

<p>Enables the use of the specified <a href="./plugins.html">plugin</a> in the wiki. 
Note that plugin names are case sensitive.</p></li>
<li><p>--disable-plugin name</p>

<p>Disables use of a plugin. For example "--disable-plugin htmlscrubber"
to do away with HTML sanitization.</p></li>
<li><p>--libdir directory</p>

<p>Makes ikiwiki look in the specified directory first, before the regular
locations when loading library files and plugins. For example, if you set
libdir to "/home/you/.ikiwiki/", you can install a foo.pm plugin as
"/home/you/.ikiwiki/IkiWiki/Plugin/foo.pm".</p></li>
<li><p>--discussion, --no-discussion</p>

<p>Enables or disables "Discussion" links from being added to the header of
every page. The links are enabled by default.</p></li>
<li><p>--numbacklinks n</p>

<p>Controls how many backlinks should be displayed at the bottom of a page.
Excess backlinks will be hidden in a popup. Default is 10. Set to 0 to
disable this feature.</p></li>
<li><p>--userdir subdir</p>

<p>Optionally, allows links to users of the wiki to link to pages inside a
subdirectory of the wiki. The default is to link to pages in the toplevel
directory of the wiki.</p></li>
<li><p>--htmlext html</p>

<p>Configures the extension used for generated html files. Default is "html".</p></li>
<li><p>--timeformat format</p>

<p>Specify how to display the time or date. The format string is passed to the
strftime(3) function.</p></li>
<li><p>--verbose, --no-verbose</p>

<p>Be verbose about what is being done.</p></li>
<li><p>--syslog, --no-syslog</p>

<p>Log to syslog(3).</p></li>
<li><p>--usedirs, --no-usedirs</p>

<p>Toggle creating output files named page/index.html (default) instead of page.html.</p></li>
<li><p>--prefix-directives, --no-prefix-directives</p>

<p>Toggle new '!'-prefixed syntax for preprocessor directives.  ikiwiki currently
defaults to --prefix-directives.</p></li>
<li><p>--w3mmode, --no-w3mmode</p>

<p>Enable <a href="./w3mmode.html">w3mmode</a>, which allows w3m to use ikiwiki as a local CGI script,
without a web server.</p></li>
<li><p>--sslcookie</p>

<p>Only send cookies over an SSL connection. This should prevent them being
intercepted. If you enable this option then you must run at least the 
CGI portion of ikiwiki over SSL.</p></li>
<li><p>--gettime, --no-gettime</p>

<p>Extract creation and modification times for each new page from the
the revision control's log. This is done automatically when building a
wiki for the first time, so you normally do not need to use this option.</p></li>
<li><p>--set var=value</p>

<p>This allows setting an arbitrary configuration variable, the same as if it
were set via a setup file. Since most commonly used options can be
configured using command-line switches, you will rarely need to use this.</p></li>
<li><p>--set-yaml var=value</p>

<p>This is like --set, but it allows setting configuration variables that
use complex data structures, by passing in a YAML document.</p></li>
</ul>

<h1>EXAMPLES</h1>

<ul>
<li><p>ikiwiki --setup my.setup</p>

<p>Completely (re)build the wiki using the specified setup file.</p></li>
<li><p>ikiwiki --setup my.setup --refresh</p>

<p>Refresh the wiki, using settings from my.setup, and avoid
rebuilding any pages that have not changed. This is faster.</p></li>
<li><p>ikiwiki --setup my.setup --refresh --wrappers</p>

<p>Refresh the wiki, including regenerating all wrapper programs,
but do not rebuild all pages. Useful if you have changed something
in the setup file that does not need a full wiki rebuild to update
all pages, but that you want to immediately take effect.</p></li>
<li><p>ikiwiki --rebuild srcdir destdir</p>

<p>Use srcdir as source and build HTML in destdir, without using a
setup file.</p></li>
<li><p>ikiwiki srcdir destdir</p>

<p>Use srcdir as source to update changed pages' HTML in destdir,
without using a setup file.</p></li>
</ul>

<h1>ENVIRONMENT</h1>

<ul>
<li><p>CC</p>

<p>This controls what C compiler is used to build wrappers. Default is 'cc'.</p></li>
<li><p>CFLAGS</p>

<p>This can be used to pass options to the C compiler when building wrappers.</p></li>
</ul>

<h1>SEE ALSO</h1>

<ul>
<li><a href="./ikiwiki-mass-rebuild.html">ikiwiki-mass-rebuild</a>(8)</li>
<li><a href="./ikiwiki-update-wikilist.html">ikiwiki-update-wikilist</a>(1)</li>
<li><a href="./ikiwiki-transition.html">ikiwiki-transition</a>(1)</li>
</ul>

<h1>AUTHOR</h1>

<p>Joey Hess <a href="mailto:joey@ikiwiki.info">&#x6A;&#111;&#101;&#121;&#64;i&#107;i&#119;&#105;&#x6B;&#105;&#46;&#x69;&#x6E;&#x66;&#x6F;</a></p>

<p>Warning: Automatically converted into a man page by mdwn2man. Edit with care</p>

</div>







</div>

<div id="footer" class="pagefooter" role="contentinfo">

<div id="pageinfo">






<div id="backlinks">
Links:

<a href="./index.html">index</a>

<a href="./plugins.html">plugins</a>

<a href="./rcs/git.html">rcs/git</a>

<a href="./setup.html">setup</a>

<a href="./setup/byhand.html">setup/byhand</a>


</div>






<div class="pagedate">
Last edited <span class="date">Tue Feb 26 23:01:54 2019</span>
<!-- Created <span class="date">Tue Feb 26 23:01:54 2019</span> -->
</div>

</div>


<!-- from ikiwiki -->
</div>

</div>

</body>
</html>