-So you want to set up your own wiki using ikiwiki? This tutorial will walk
-you through setting up a wiki that is stored in [[Subversion]], [[Git]],
-[[TLA]] or [[Mercurial]], and that has optional support for commits from the web.
-
-1. [[Install]] ikiwiki. See [[download]] for where to get it.
-
-2. Decide where your wiki's files will go.
-
- Pick three directories for respectively the repository (contains
- the "master copy" and history); working copy (checked-out
- files from the repository); and web pages (served by the web server).
-
- For the purposes of this tutorial, we'll set shell variables
- for these locations, and use those variables in the commands that follow.
-
- REPOSITORY=~/wikirepo
- SRCDIR=~/wikiwc
- DESTDIR=~/public_html/wiki/
-
-3. Create the master rcs repository for your wiki.
-
- # Subversion
- svnadmin create $REPOSITORY
- svn mkdir file://$REPOSITORY/trunk -m create
-
- # Git
- mkdir $REPOSITORY
- cd $REPOSITORY
- git init-db
- # Git requires something be in the repo to start with.
- cp /usr/share/ikiwiki/basewiki/index.mdwn .
- git add .
- git commit -m create -a
- # No need to keep files in the master repository; so at this
- # stage, you may want to remove all files (except .git) to
- # save disk space.
-
- # TLA
- mkdir $REPOSITORY
- tla make-archive me@localhost--wiki $REPOSITORY
- tla my-id "<me@localhost>"
-
- # Mercurial
- hg init $REPOSITORY
-
-4. Check out the repository to make the working copy that ikiwiki will use
- as its source directory.
-
- # Subversion
- svn co file://$REPOSITORY/trunk ~/wikiwc
-
- # Git
- # Create a local clone to save disk space and also to
- # optimize performance. See git-clone(1).
- git clone -l -s $REPOSITORY $SRCDIR
-
- # TLA
- mkdir $SRCDIR
- cd $SRCDIR
- tla archive-setup me@localhost--wiki/wiki--0
- tla init-tree me@localhost--wiki/wiki--0
- # Edit {arch}/=tagging-method and change the precious
- # line to add the .ikiwiki directory to the regexp.
- tla import
-
- # Mercurial
- # Mercurial uses a single repo approach, so no need to
- # clone anything. Because the following examples
- # refer to $SRCDIR, we symlink it:
- ln -s $REPOSITORY $SRCDIR
-
-5. Build your wiki for the first time.
-
- ikiwiki --verbose $SRCDIR $DESTDIR \
- --url=http://host/~you/wiki/
-
- Replace the url with the real url to your wiki. You should now
- be able to visit the url and see your wiki.
-
-6. Customise your wiki. The files in `/usr/share/ikiwiki/basewiki/` are
- used if you don't have a custom version, so let's start by making a
- custom version of the wiki's index page:
-
- cd $SRCDIR
- cp /usr/share/ikiwiki/basewiki/index.mdwn .
- $EDITOR index.mdwn
-
- # Subversion
- svn add index.mdwn
- svn commit -m customised index.mdwn
-
- # Git
- git add index.mdwn
- git commit -m customised index.mdwn
- git push origin
-
- # TLA
- tla add index.mdwn
- tla commit
-
- # Mercurial
- hg add index.mdwn
- hg commit -m customised index.mdwn
-
- You can also add any files you like from scratch of course. Use the same
- command as in step 5 to rebuild the wiki.
-
-7. Repeat steps 5 and 6 as desired, editing or adding pages and rebuilding
- the wiki. You can play around with other ikiwiki parameters such as
- `--wikiname` and `--rebuild` too. Get comfortable with its command line
- (see [[usage]]).
-
-8. By now you should be getting tired of typing in all the command line
- options each time you change something in your wiki's setup. And it's
- also getting old to have to manualy rebuild the wiki each time you
- change a file. Time to introduce setup files.
-
- A sample setup file is [[ikiwiki.setup]]. Download it (or copy it from
- `doc/ikiwiki.setup` in the ikiwiki sources), and edit it.
+This tutorial will walk you through setting up a wiki with ikiwiki.
+
+[[!toc ]]
+
+## Install ikiwiki
+
+If you're using Debian or Ubuntu, ikiwiki is an `apt-get install ikiwiki` away.
+If you're not, see the [[download]] and [[install]] pages.
+
+## Create your wiki
+
+All it takes to create a fully functional wiki using ikiwiki is running
+one command.
+[[!template id=note text="""
+For more control, advanced users may prefer to set up a wiki
+[[by_hand|byhand]].
+"""]]
+
+ % ikiwiki -setup /etc/ikiwiki/auto.setup
+
+Or, set up a blog with ikiwiki, run this command instead.
+
+ % ikiwiki -setup /etc/ikiwiki/auto-blog.setup
+
+Either way, it will ask you a couple of questions.
+
+ What will the wiki be named? foo
+ What revision control system to use? git
+ What wiki user (or openid) will be admin? joey
+ Choose a password:
+
+Then, wait for it to tell you an url for your new site..
+
+ Successfully set up foo:
+ url: http://example.com/~joey/foo
+ srcdir: ~/foo
+ destdir: ~/public_html/foo
+ repository: ~/foo.git
+ To modify settings, edit ~/foo.setup and then run:
+ ikiwiki -setup ~/foo.setup
+
+Done!
+
+## Using the web interface
+
+Now you can go to the url it told you, and edit pages in your new wiki
+using the web interface.
+
+(If the web interface doesn't seem to allow editing or login, you may
+need to configure [[configure_the_web_server|tips/dot_cgi]].)
+
+## Checkout and edit wiki source
+
+Part of the fun of using ikiwiki is not being limited to using the
+web for editing pages, and instead using your favorite text editor and
+[[Revision_Control_System|rcs]].
+
+To do this, you need to check out a copy of the source to your wiki.
+(You should avoid making changes directly to the `srcdir`, as that
+checkout is reserved for use by ikiwiki itself.)
+
+Depending on which [[Revision_Control_System|rcs]] you chose to use,
+you can run one of these commands to check out your own copy of your wiki's
+source. (Remember to replace "foo" with the real directory name.)
+
+ git clone foo.git foo.src
+ svn checkout file://`pwd`/foo.svn/trunk foo.src
+ bzr clone foo foo.src
+ hg clone foo foo.src
+ # TODO monotone, tla
+
+Now to edit pages by hand, go into the directory you checked out (ie,
+"foo.src"), and fire up your text editor to edit `index.mdwn` or whatever
+other page you want to edit. If you chose to set up a blog, there is even a
+sample first post in `posts/first_post.mdwn` that you can edit.
+
+Once you've edited a page, use your revision control system to commit
+the changes. For distributed revision control systems, don't forget to push
+your commit.
+
+Once the commit reaches the repository, ikiwiki will notice it, and
+automatically update the wiki with your changes.
+
+## Customizing the wiki
+
+There are lots of things you can configure to customize your wiki.
+These range from changing the wiki's name, to enabling [[plugins]],
+to banning users and locking pages.
+
+If you log in as the admin user you configured earlier, and go to
+your Preferences page, you can click on "Wiki Setup" to customize many
+wiki settings and plugins.
+
+Some settings cannot be configured on the web, for security reasons or
+because misconfiguring them could break the wiki. To change these settings,
+you can manually edit the setup file, which is named something like
+"foo.setup". The file lists all available configuration settings
+and gives a brief description of each.
+
+After making changes to this file, you need to tell ikiwiki to use it:
+
+ % ikiwiki -setup foo.setup
+
+## Customizing file locations
+
+As a wiki compiler, ikiwiki builds a wiki from files in a source directory,
+and outputs the files to a destination directory. The source directory is
+a working copy checked out from the version control system repository.
+
+When you used `auto.setup`, ikiwiki put the source directory, destination
+directory, and repository in your home directory, and told you the location
+of each. Those locations were chosen to work without customization, but you
+might want to move them to different directories.
+
+First, move the destination directory and repository around.