简体中文MoinMoin/安装手册

Basic Installation

Before you can integrate MoinMoin into your web environment, you have to install the MoinMoin source code and data files using the standard Python distutils mechanism (setup.py). This page explains the steps you usually need to take to do this. For more details on the distutils installation process, consult the Installing Python Modules document in your Python documentation set.

The installation is similar on Windows and Linux (and other POSIX-type systems; for simplicity, we just say "Linux" in the docs).

• We use text such as > command arguments to show what you have to type at the command prompt (also known as shell, terminal, etc.). In our examples "> " is the prompt, you don't have to type it in, you have to type what comes after it. Lines that do not begin with "> " are the answers to the commands you have typed. Read them carefully.

Check if Python is working

MoinMoin needs Python to run, so the first step is to check if an usable version of Python is installed and correctly set-up. If this is not the case, you will have to fix that before you can proceed.

The CHANGES file in the MoinMoin archive mentions what versions are supported. Python 2.2.2 is the minimum requirement for MoinMoin 1.3, but we suggest you use the latest Python 2.3.x version because Python 2.2.x has annoying known bugs. You can use Python 2.4.x if you want, it works well too.

You can download Python at http://www.python.org/download/.

If you are pretty sure an acceptable version of Python is installed but the commands below do not work, this may be because your Python files are not in the search path. Correctly setting the search path is outside the scope of this document; please ask for help on your favorite Python, Linux, or Windows discussion board.

If you have shell access, checking if Python is working is very simple. Just type the following command, and look at the result:

> python -V
Python 2.3.4

If you don't have shell access, you can try using this pythontest.cgi script (it assumes that you are using a Linux kind of webserver). Upload the script to your cgi-bin directory, use chmod a+rx pythontest.cgi (or a similar command in your FTP program) to make it executable, and invoke it using your web browser.

#!/bin/sh
echo Content-Type: text/plain
echo
echo "Your web server is running as:"
id
echo "CGI scripts work"
echo "Now we try to invoke Python interpreters and get their versions:"
python -V 2>&1
python2 -V 2>&1
python2.0 -V 2>&1
python2.1 -V 2>&1
python2.2 -V 2>&1
python2.3 -V 2>&1
python2.4 -V 2>&1
echo "Finished."

If it doesn't display "CGI scripts work", well, then CGI scripts don't work. If it doesn't show one or more Python version numbers, you have to make sure that Python is correctly installed.

Download MoinMoin

To download the distribution archive, go to the download area and fetch the lastest archive.

Unpack the archive

The next step is to unpack the distribution archive (which you have done already if you are reading this text from your hard drive). If you read this on the web, the distribution comes in a versioned .zip or .tar.gz archive, which you can unpack as shown below.

• On Windows

  • You can use a program like WinZip, which handles both kinds of archives.

  • At the command prompt, you can use gnuzip and gnutar for Windows.

• On Linux

  • Your favorite file manager should be able to unpack them.

  • At any shell prompt, the unzip and tar commands can be used to unpack them.

The distribution archive will always unpack into a directory named moin-<version>, for example moin-1.3.

Here is how you would unpack the archive (using GNU tar) and enter the directory with the MoinMoin files:

> tar xzf moin-1.3.tar.gz
> cd moin-1.3

Install MoinMoin

You can install MoinMoin to either:

• a system location (if you have the necessary rights to do that -- on Linux you need to be root)

• some specific location, like your home directory (Linux) or C:\moin (Windows).

The installation to a system location is easier, so choose that if possible.

If you have several versions of Python installed, please use the same version for setup and for running the wiki. Usually, the latest Python version will get the best results.

Note: On Linux, if you have problems with the setup.py install step, you may need to have the Python development files installed. Some Linux distribution put them in a separate package, not installed by default. For example, on Mandrake you need to "rpm -i python-devel-2.x.x-xmdk.i586.rpm".

Installing in the default system location

> python setup.py --quiet install --record=install.log

This installs MoinMoin to the default system location (typically the Python directory, for example on Linux, inside /usr/lib and /usr/share). Look at the install.log file to see what was installed, and where.

Installing in the home directory or another specific location

Linux example, installing in the home directory:

> python setup.py --quiet install --prefix=$HOME --record=install.log

Windows example, installing in the C:\moin directory:

> python setup.py --quiet install --prefix=C:\moin --record=install.log

All MoinMoin files will then be installed inside those directories, see install.log to know which files were installed, and where.

Note: You will likely see the following warning:

• warning: install: modules installed to 'C:\moin\', which
  is not in Python's module search path (sys.path) -- you'll
  have to change the search path yourself

This means exactly what it says, you need to add your install directory to the search path of Python, or it won't find the MoinMoin code.

For example, if you are running using a webserver and standard CGI, edit moin.cgi and add your installation directory to the Python path, like this:

import sys
sys.path.append('C:/moin')

Check that everything is working correctly

As a final step, if you have access to the shell or the command prompt, you can check that everything is correctly installed and ready to run. Start Python and type import MoinMoin. Nothing should be displayed in response to this command. Example:

> python
Python 2.3.4 (#1, May 29 2004, 17:05:23)
[GCC 3.3.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import MoinMoin
>>>

If you get this instead:

>>> import MoinMoin
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
ImportError: No module named MoinMoin
>>>

then you have to tune your installation. Try modifying sys.path, as described above.

What you have now

So, you have a ready-to-work MoinMoin installation now. Congratulations! Before you go on to configuring it, take a look at the various files and directories that have been installed.

It is important that you understand the different locations used in a MoinMoin setup, so read this carefully.

In the following descriptions, PREFIX is what you used with the setup.py command, or a default location when you didn't use the --prefix option. Typical default values are /usr and /usr/local. X and Y are the main version and the subversion of Python. Typically, X is 2 and Y is 3 or 4.

Look into install.log to find out about following important locations:

• MoinMoin directory, usually PREFIX/lib/pythonX.Y/site-packages/MoinMoin -- this is where the MoinMoin code is located

• share directory, usually PREFIX/share/moin - this is where the templates are located

  • data directory (wiki pages, users, etc.) - only MoinMoin should access this

  • underlay directory (wiki pages, users, etc.) - only MoinMoin should access this

  • htdocs directory with themes (images and CSS) and a few other files - the web server will need to access this

  • server - MoinMoin example startup files (like moin.cgi for CGI and other files for other startup methods)

  • config - MoinMoin example configuration files (like wikiconfig.py)

• bin directory with some scripts that help you use the MoinMoin shell commands

We talk of templates in the share directory because you usually will not use those files at that location, but copy them elsewhere when you need them. This way, you can set-up several wikis without problems, and easily upgrade to new MoinMoin versions.

Creating a wiki instance

After you have downloaded and installed MoinMoin, you will want to "have a wiki". As explained at the bottom of ../BasicInstallation, you have to copy several directories and files. This way, you can have as many wikis as you want, and you can easily upgrade MoinMoin: only the original files will be overwritten, not your copies.

Every time you copy those files (and modify the configuration of your server accordingly), you create what is called a wiki instance. Each wiki instance is independant from the others, with a different configuration, different pages, different users, etc.

Some of the steps you need to take depend on which web server and which operating system you use. They are described on dedicated pages, which you should read (at least the beginning) before reading this one. Some other steps are common to every webserver and operating system (copying files around, setting permissions), and this is what is described here.

Security warning

Make sure that your data directory and your configuration files are not accessible through your web server. Do not put your wiki files in public_html, Sites or any other directory your web server can access. The web server only needs to access the file in the htdocs directory and the moin.cgi script! (Or whatever script your server uses to start MoinMoin.)

Also make sure that the data directory and its subdirectories are not readable and not writeable by users other than the web server user (and of course, the administrator of the machine, like root). If you need to give worldwide read-write permissions to get it working, be aware that you are doing a very unsecure setup, that can be compromised by any other user of your computer.

Note to Windows users

All the commands below are Linux commands. The text descriptions that surround them should be enough to help you understand what you need to do. Use the Windows Explorer, or the equivalent text-mode commands.

Choose a name

Choose a unique name for the new wiki instance you want to create. It should be a short word, something that reflects what you intend to use the wiki for, like the name of your organization, of your team, of the project you are working on, etc. Unfortunately, you cannot use "wiki", because MoinMoin uses it internally for other purposes.

• Do not use the name "wiki", it is reserved for internal use.

The name "mywiki" is used as an example in the various commands below.

Choose a location

Choose a directory on your server, it will contain all the files needed for your wiki instance. At the beginning, your wiki instance will use approximately 10 MB of disk space. Then of course, it will grow depending on the way your wiki is used. A personal wiki, even with many pages, might only use 30 MB or 40 MB of disk space. A popular wiki, or a wiki with many files attached to the pages, might use much more, of course.

If you are the administrator (or root) of the server, you can use anything you like or that makes sense to you, for example /usr/local/var/moin, /mnt/wikis, etc.

If you are a simple user, you will probably only be allowed to write in your personal, "home" directory. Choose a subdirectory that makes sense to you, for example the share/moin subdirectory.

Collect some important information

This is where the instructions differ according to the web server and operating system you use, and whether you are the administrator or a simple user. See the appropriate pages for your web server and operating system combination.

On Linux, the export command will be used to remember the collected information. Windows users should write them down carefully (maybe cutting-and-pasting in a Notepad window), or store them in environment variables if they use the command prompt.

• PREFIX is the prefix you used during the ../BasicInstallation

• SHARE is the name of the share directory, as discussed at the bottom of ../BasicInstallation

• WIKILOCATION is the name of the directory that will contain your wiki instance

If you are an administrator, you also need to collect the following:

• USER is the user name used by the web server

• GROUP is the name of the group to which the web server belongs

Now, Linux folks, let's store these settings in memory:

> export PREFIX=/usr                # this might be something else
> export SHARE=$PREFIX/share/moin   # this should be correct for most people
> export WIKILOCATION=$SHARE        # this is just an example
> export INSTANCE=mywiki            # this is just an example

Administrators also need the following two lines:

> export USER=www-data              # the usual setting of the Apache server on Linux
> export GROUP=www-data             # the usual setting of the Apache server on Linux

Copy the files

To create your new instance, you first need to create a directory named like your instance, inside the WIKILOCATION. Then you need to copy the data and underlay directories from your SHARE directory into your instance directory. Finally, you need to copy the wikiconfig.py file from the config directory into the instance directory.

Linux folks need just use these commands:

> cd $WIKILOCATION
> mkdir $INSTANCE                   # make a directory for this instance
> cp -R $SHARE/data $INSTANCE       # copy template data directory
> cp -R $SHARE/underlay $INSTANCE   # copy underlay data directory
> cp $SHARE/config/wikiconfig.py $INSTANCE   # copy wiki configuration sample file

Set permissions

Administrators

Administrators need to restrict the permissions of the files, so that only the web server (and the administrator of course) can read and write them. For maximum security, no other user on the machine should be able to read or write anything in the wiki instance directory. Don't forget that this directory contains sensitive information, notably the (encrypted) passwords of the wiki users.

On Linux, the following commands should be enough:

> chown -R $USER.$GROUP $INSTANCE   # check that USER and GROUP are correct
> chmod -R ug+rwX $INSTANCE         # USER.GROUP may read and write
> chmod -R o-rwx $INSTANCE          # everybody else is rejected

Normal users

Normal users, on the contrary, need to broaden the permissions of the files, so that the web server can read and write them. On recent Windows versions, and on some versions of Unix, Linux and other systems, access control lists can be used to that effect. They are, however, powerful and complicated, much beyond the scope of this document. Ask a knowledgeable person about them.

Without them, normal users have to allow everybody to access the instance directory. This is the only way the web server can enter it and do its work. This is, of course, VERY INSECURE, since any other user and program on the server can read the directory. You should not use such a setup for a wiki open to the public.

Note: it is also possible to put the web server and the normal user in the same group, and then only open the instance directory to the members of that group. This is a bit more secure (depending on who else is in the group), but you need the cooperation of the server administrator; he is the one setting up groups.

On Linux, the following commands will open the instance directory to the whole world:

> chmod -R a+rwX $INSTANCE/data
> chmod -R a+rwX $INSTANCE/underlay

Tune configuration

Now, you need to tune the configuration of your web server and of your wiki instance. Look at the appropriate help page for your web server, then come here to tune the settings of your wiki instance.

Edit wikiconfig.py. The default settings should work fine in most cases, but there are some things that you will probably want to change, like the name and logo of your wiki! Read the comments inside wikiconfig.py, they will guide you through this process. (Start with "Wiki identity", around line 25.)

HelpOnConfiguration contains all the details about all the options, in case the comments in wikiconfig.py are not enough.

This page describes the particular steps that need to be taken when you use MoinMoin on Linux with the Apache web server. You should have already performed the ../BasicInstallation.

Two scenarios are possible. You might be the administrator (root or webmaster) of the server, able to install and modify files almost anywhere on the machine, and notably able to modifiy the Apache configuration. You might also be a simple user, only able to write files into your home directory, and unable to alter the master Apache config file. The two scenarios are discussed below.

Table of contents

1. Administrator (root)
   1. Create a wiki instance
   2. Install moin.cgi
   3. Configure moin.cgi
   4. Configure Apache
   5. Configure MoinMoin
   6. Final test
2. Simple user (home directory installation)
   1. Make sure /~username works
   2. Create a wiki instance
   3. Install the htdocs files
   4. Install moin.cgi
   5. Configure moin.cgi
   6. Configure MoinMoin
   7. Final test
3. Troubleshooting
   1. Adding permission to serve the htdocs directory

Administrator (root)

Most GNU/Linux distributions come with Apache pre-installed. There is, however, some variation as to where exactly the various Apache files are located. You should consult your distribution manual, or ask on the appropriate discussion board. In the following paragraphs, we assume a (quite standard) file system layout with:

• /etc/httpd/httpd.conf - the main httpd configuration file

• /var/log/httpd/error_log - the log file containing Apache error messages

Some distributions use apache instead of httpd for the directory names, others may use weirder settings.

Create a wiki instance

Creating a wiki instance involves copying files around and setting appropriate permissions. Before you can proceed, you need to know what user and group your Apache server runs on. The easiest way to know this is to issue this command:

> egrep "^User|^Group" /etc/httpd/httpd.conf
User wwwrun
Group nogroup

This shows a typical result: "wwwrun.nogroup". Other typical results are "nobody.nogroup" and "www-data.www-data". You can of course use your own. What matters is that you know which ones are in use, because you will need them to set file permissions.

Once you have gathered this information, read ../WikiInstanceCreation and follow the steps described there.

Install moin.cgi

There is one last file you need to copy, the bridge between Apache and MoinMoin: the CGI script that Apache will call every time a wiki page is requested, and that will in turn invoke all the MoinMoin components to handle the request. You can actually put this script anywhere you like (all the paths to the files MoinMoin needs can be configured to match your filesystem layout), but for the sake of simplicity and security, we suggest you follow the instructions below, unless you think you know better.

We will create a cgi-bin subdirectory in the instance directory. Using the environment variables defined in ../WikiInstanceCreation, run the following commands:

> cd $WIKILOCATION/$INSTANCE
> mkdir cgi-bin
> cp $SHARE/server/moin.cgi cgi-bin
> chown -R $USER.$GROUP cgi-bin
> chmod -R ug+rx cgi-bin
> chmod -R o-rwx cgi-bin

Configure moin.cgi

When moin.cgi is launched, it imports a MoinMoin module (that in turn imports other modules and the configuration file). While the MoinMoin modules should always be found in a properly configured system (as described in ../BasicInstallation), it is likely that the configuration file will not be found. Edit the moin.cgi script to correct that. Add these lines near the top of the file:

import sys
sys.path.insert(0, '..')

You can also use the absolute name of the directory that contains the wikiconfig.py file instead of '..'.

Configure Apache

Now that every file is in place and properly locked down (as far as the filesystem is concerned), we need to configure Apache so that it offers access to the right files, and no others. However, since the default Apache configuration varies a lot according to the distribution you use, and since administrators often make important additions and changes to it, we cannot give exact instructions that cover all cases. Instead, we will first describe roughly what needs to be done, and then give a few specific lines that you should add at the appropriate place in your Apache config.

Your Apache should be set up so that:

• Access to your instance directory is denied (sane Apache installations should actually deny access to the whole server, and then only allow a few specific directories).

• An alias is set up to redirect requests from /wiki/ (in the URL) to the htdocs directory (in the share directory, as discussed at the bottom of ../BasicInstallation)

• A script alias is set up to redirect requests from whatever you want (we suggest you use your instance name, for example /mywiki) to the CGI script you just copied.

The following commands will add two lines at the bottom of your Apache config file. These lines only cover the last two items listed above. You have to check the first one by yourself (there is too much variation in Linux distributions). Note that you may have to move the two lines around in your config file -- maybe near other similar lines.

> echo "" >>/etc/httpd/httpd.conf
> echo "Alias /wiki/ \"$SHARE/htdocs/\"" >>/etc/httpd/httpd.conf
> echo "ScriptAlias /mywiki \"$WIKILOCATION/$INSTANCE/cgi-bin/moin.cgi\"" >>/etc/httpd/httpd.conf

You only need to define the alias for htdocs once. You need of course to define a different script alias for each wiki instance you intend to run.

Configure MoinMoin

Finally, check that the wikiconfig.py file in the instance directory contains correct paths for the htdocs prefix, the instance data directory, and the instance underlay directory. You can use relative paths for the directories, but note that they are relative to the CGI script, not the configuration file! You can also use absolute paths, and save yourself some headaches.

Here are the settings you should have in the config file if you followed all our suggestions:

    data_dir = '../data/'
    data_underlay_dir = '../underlay/'
    url_prefix = '/wiki'

There are other settings you will likely want to alter, look at the bottom of ../WikiInstanceCreation for more details about them.

Final test

Everything should work fine, now. It is time to restart the Apache server (usually "/etc/init.d/apache restart", sometimes also "apachectl restart") and perform the following steps:

• Try to access your new-born wiki with the URL "http://127.0.0.1/mywiki/" (or the name and port you have defined in the Apache configuration file, of course). You should see the FrontPage.

• If this is the case, try to edit it and save your changes.

• If that works, see if your edit is reflected on the RecentChanges page.

• If you see them, congratulations, you have a new wiki!

If something goes wrong, have a look at Troubleshooting, at the bottom of this page.

Simple user (home directory installation)

On machines shared by many people, simple users typically have no access to the root account, cannot modify the httpd.conf file, and cannot copy files into the system-wide cgi-bin and htdocs directories. In that case, Apache can be set up so that each user can host a web site in the home directory of his or her shell account, using the UserDir directive. If the machine administrator decides to use it, all URLs that start with "/~username" will be redirected to a directory in the users' home directories, where they have write permission and can install MoinMoin.

As an example, we will consider the case of a user named "mm". Of course, wherever you see "mm" below, you will replace it with your own username.

Make sure /~username works

The home directory installation can only work if the administrator (root) has allowed it. So, the first step is of course to check that it works. Typically, Apache is set up so that the public_html subdirectory in the home directory is used as the web site root. So, the first first step is to check if that directory exists.

> ls -ld ~/public_html
drwxr-xr-x   2 mm       users        4096 Nov 30 00:29 public_html

If the directory does not exist, create it, and be sure it can be read and entered by the web server.

> mkdir public_html
> chmod a+rx public_html
> ls -ld ~/public_html
drwxr-xr-x   2 mm       users        4096 Nov 30 00:35 public_html

Now, check if the "/~mm" URL works:

> lynx -error_file=/dev/stderr -dump http://localhost/~mm/ >/dev/null
URL=http://localhost/~mm/ (GET)
STATUS=HTTP/1.1 200 OK

If you get a "200 OK" response code, then it works, and you can go on to the next check. If you get a "403 Forbidden" or a "404 Not Found" response, then maybe something is wrong with your directory, or maybe the whole thing has not been enabled by your administrator.

• Check the permissions for your home directory (~) and your public_html directory. The first one should at least end with "--x", and the second one, as we saw above, with "r-x".

• It also possible that the administrator has set up another name for the personal web site directory. "public_html" is just the usual default, but anything can actually be used. There is no way to know, you have to ask the administrator (root or webmaster).

• Finally, if the personal web site feature is disabled, maybe you can ask the administrator to enable it?

Once you have checked you can read the files in the directory, you need to check that you are also able to execute CGI scripts in that directory. Use the following commands to create a simple CGI script in the appropriate location:

> mkdir -p ~/public_html/cgi-bin
> cat > ~/public_html/cgi-bin/test.cgi
#!/bin/sh
echo Content-Type: text/plain
echo
echo "CGI scripts work"
<CTRL-D>
> chmod a+rx ~/public_html/cgi-bin/test.cgi
> lynx -dump http://localhost/~jh/cgi-bin/test.cgi
CGI scripts work

If you get anything else than "CGI scripts work", then something went wrong. Check the directory permissions as above, try other names (or ask about them). The sad truth might be that you are not allowed to execute CGI scripts. You would then have to ask the administrator (or webmaster) for that permission.

Once you get it, you can set up your wiki instance in the public_html directory.

Create a wiki instance

Creating a wiki instance involves copying files around and setting appropriate permissions. Read ../WikiInstanceCreation and follow the steps described there.

Install the htdocs files

The web server needs to access these files, so we need to copy them in the "public_html" directory. Just use this:

> cd ~/public_html
> cp -R ~/share/moin/htdocs wiki
> chmod -R a+rX wiki

Install moin.cgi

There is one last file you need to copy, the bridge between Apache and MoinMoin: the CGI script that Apache will call every time a wiki page is requested, and that will in turn invoke all the MoinMoin components to handle the request. You need to put this file in a directory for which CGI scripts execution is enabled. By default, this should work:

> cd ~/public_html
> mkdir cgi-bin
> cp $SHARE/server/moin.cgi cgi-bin
> chmod -R a+rx cgi-bin

Configure moin.cgi

When moin.cgi is launched, it imports a MoinMoin module (that in turn imports other modules and the configuration file). Since everything has been installed in your home directory, it is likely none of these will be found. Edit the moin.cgi script to correct that. Add these lines near the top of the file:

import sys
sys.path.insert(0, '/home/mm/lib/python2.3')
sys.path.insert(0, '/home/mm/lib/python2.3/site-packages')
sys.path.insert(0, '/home/mm/share/moin/mywiki')

Of course, you need to adapt the paths to your situation. The first two lines should help locate the MoinMoin modules, the last one should help locate the wikiconfig.py file.

Note: You might also need to edit the first line of the file, to point to the correct version of Python. The default should be fine, but a line like "#! /usr/bin/python2.3" might help you if the default does not work.

Configure MoinMoin

Finally, check that the wikiconfig.py file in the instance directory contains correct paths for the htdocs directory, the instance data directory, and the instance underlay directory. You can use relative paths for the directories, but note that they are relative to the CGI script, not the configuration file! You can also use absolute paths, and save yourself some headaches.

    data_dir = '/home/mm/share/moin/mywiki/data/'
    data_underlay_dir = '/home/mm/share/moin/mywiki/underlay/'
    url_prefix = '/~mm/wiki'

Final test

Everything should work fine, now. It is time to perform the following steps:

• Run the MoinMoin CGI Diagnosis: > lynx -dump http://localhost/~mm/cgi-bin/moin.cgi?action=test

• If it worked, try to access your new-born wiki with the URL "http://127.0.0.1/~mm/cgi-bin/moin.cgi". You should see the FrontPage.

• If this is the case, try to edit it and save your changes.

• If that works, see if your edit is reflected on the RecentChanges page.

• If you see them, congratulations, you have a new wiki!

If something goes wrong, have a look at Troubleshooting, below.

Troubleshooting

See also ../TroubleShooting for generic stuff.

The first thing to do when your wiki does not work as expected is to issue the command "tail /var/log/httpd/error_log" to display the most recent errors. Usually, you will get a hint on what went wrong, like missing file system permissions.

Adding permission to serve the htdocs directory

In some (sane) Linux distributions (like SuSE 9.0) serving directories other than the document-root "/srv/www/htdocs" with Apache is switched off by default for security reasons in "/etc/httpd/httpd.conf" (or for Apache2 "/etc/apache2/httpd.conf"):

# forbid access to the entire filesystem by default
<Directory />
  Options None
  AllowOverride None
  Order deny, allow
  Deny from all
</Directory>

To allow Apache to serve directories outside of the document root you have to add these lines to "/etc/httpd/httpd.conf" (in SuSE it is recommended to create a new "http.conf.local" and include this file in "/etc/sysconfig/apache2"):

Alias /wiki/ "/usr/share/moin/htdocs/"
<Directory "/usr/share/moin/htdocs/>
   Order deny,allow
   Allow from all
</Directory>

ScriptAlias /mywiki "/usr/share/moin/mywiki/cgi-bin/moin.cgi"
<Directory "/usr/share/moin/mywiki/cgi-bin/moin.cgi">
   Order deny,allow
   Allow from all
</Directory>

Of course, you need to adapt the paths to your particular situation.

Using MoinMoin with apache + mod_fastcgi

FastCGI is a method which enables apache to communicate with long-running scripts. This has the advantage that the script is only started and initialized one time, and that data could be cached in memory from request to request, enhancing the performance of the CGI application.

Deploying MoinMoin with apache + mod_fastcgi

To deploy MoinMoin using FastCGI you need an apache with mod_fastcgi. Please refer to the documentation of mod_fastcgi how to build it.

Follow the basic apache installation for your operating system as described in other parts of the MoinMoin installation documentation. In places where the documentation refers to moin.cgi you use moin.fcg instead. Be sure that .fcg is handled by the FastCGI module (AddHandler fastcgi-script .fcg in your apache config).

Normally apache will start CGI scripts with its own user and group, or with the user and group of the !VirtualHost if you are using the suexec wrapper. To enable this with FastCGI you need to use FastCgiWrapper On in your apache config (see FastCGI Documentation).

Be sure to restart your apache, after you changed py files (i.e. the config) for a running FastCGI server, or you won't see any changes!

Using MoinMoin with apache + mod_python

mod_python embeds the python interpreter into the apache server. This saves initialization time and the need of forking cgi scripts. It doesn't have the ability to run as different users. It will always run as the main apache user and group. Be sure that your wiki data files are accessible by your apache server!

mod_python versions before 3.1.3 have a bug in apache.resolve_object This bug is fixed in version 3.1.3 an will perhaps fixed in later 2.X releases for apache 1.3.

Deploying MoinMoin with mod_python

Follow the basic apache installation for your operating system as described in other parts of the MoinMoin installation documentation. Don't copy moin.cgi, cause you won't need it. Be sure that the apache process can access the wiki data files (check User and Group in your apache.conf).

Copy the sample moin_modpy.htaccess as .htaccess to the path below which your wiki instance should be found:

cd /usr/local/share/moin
cp wiki/cgi-bin/moin_modpy.htaccess /path/to/your/docroot/.htaccess

Check the .htaccess that the PythonPath matches your installation. It should contain the path where the moin_modpy.py wrapper is installed (Note: the wrapper does not have to be within your DOCROOT). You can also change the name of your instance (<Files wikiname>).

Check sys.path of moin_modpy.py. It needs to find the MoinMoin package (not needed if MoinMoin is installed system wide) and your wikiconfig.py.

In some cases you need to restart apache after changes to py files used by mod_python. Please refer to the mod_python documentation.

reading of .htaccess

In SuSE Linux 9.0 reading of .htaccess is switched off by default in "/etc/apache2/http.conf" with

* forbid access to the entire filesystem by default
<Directory />
  Options None
  AllowOverride None
  Qrder deny, allow
  Deny from all
</Directory>

To allow Apache processing your .htaccess file (in your document root) you have to modify "/etc/apache2/http.conf" (for SuSE it is actually recommended to create a new "http.conf.local" and include it in "/etc/sysconfig/apache2").

<Directory "/src/www/htdocs"
   # this is the document root in Suse
   AllowOverride All 
</Directory>

Fixing the mod_python bug

If you did use the wrapper setup from the previous section, you don't need to do this.

mod_python has a small resolver bug in versions before 3.1.3. The method resolve_object in mod_python/apache.py checks the wrong object, and so the lookup for RequestModPy.run fails. You have two possibilities to live with it: either use the wrapper script moin_modpy.py or fix the bug.

To fix it you need to change the method resolve_object (around line 551 for mod_python 3.1.2b) from

        if silent and not hasattr(module, obj_str):
            return None

to

        if silent and not hasattr(obj, obj_str):
            return None

This bug is currently in all versions of mod_python before 3.1.3. It might be fixed in a next 2.X release for apache 1.3, too.

Deploying with a fixed mod_python

This section only works with a fixed mod_python (see previous section)!

Follow the deployment documentation above. Use the special commented out section of moin_modpy.htaccess instead of the default wrapper using part.

Check the PythonPath in the .htaccess that it matches your installation. It should contain the python lib path where the MoinMoin package is stored (not needed if MoinMoin is installed system wide) and the path to your wikiconfig.py.

The wrapper script moin_modpy.py is not needed, cause the !RequestModPy class is used directly by mod_python.

Installing to base root with ModPython

This stuff needs a security review/rewrite. Having data/ under document root or a directory configured to be available by the web server is a bad idea.

None of the above instructions work if you want to make MoinMoin work at the base url and use ModPython (i.e. http://www.myserver.com/ and not http://www.myserver.com/wiki ). Here is what worked for me for setting up MoinMoin for use with multiple virtual servers (these are instructions for modpython 3.1.3 or later):

Remember to replace "mywiki" in all these instructions with whatever name you chose.

I keep the folders for the various wikis as subdirectories of /usr/share/moin. Similar to the regular install instructions, do this after running python setup.py install for moinmoin:

cd /usr/share/moin
mkdir mywiki
cp -r data mywiki
cp config/wikiconfig.py mywiki  (this is the only file you need)
chown -R www-data:www-data mywiki (use the user and group of apache)

Edit your apache configuration file to allow the moin parent folder to override !FileInfo at least:

<Directory "/usr/share/moin">
 Options Indexes Includes FollowSymLinks MultiViews
 AllowOverride All  #you need to allow FileInfo at least
 Order allow,deny
 Allow from all
</Directory>

For your server or virtual host, you need to set at least the two Aliases:

<VirtualHost your.ip.address>
    ServerName your.server.name
    DocumentRoot /usr/share/moin/mywiki  #not really necessary
    ServerAdmin webmaster@your.server.name

    #This next line allows shared moinmoin images to load
    Alias /wiki/ "/usr/share/moin/htdocs/"

    #This is the line that passes a name to your python handler,
    #  the trailing slash is necessary
    Alias / "/usr/share/moin/mywiki/"
</VirtualHost>

Edit /usr/share/moin/mywiki/wikiconfig.py:

sitename = 'My Wiki'
interwikiname = 'MyWiki'
data_dir = '/usr/share/moin/mywiki/data/'  #this needs to be a FULL path

And most importantly, you need to add an .htaccess file under /usr/share/moin/wiki1/ (or else add these lines to your main httpd.conf file:

# PythonDebug On
<Files mywiki>
  SetHandler python-program
  PythonPath "['/usr/share/moin/mywiki/']+sys.path"
  PythonHandler MoinMoin.request::RequestModPy.run
</Files>

Using MoinMoin with Twisted

Twisted is a standalone python framework for many kinds of applications. For MoinMoin, we use Twisted as a python web server that just imports MoinMoin persistently.

This has the advantage that the Python interpreter and all Python scripts (including Twisted itself and also MoinMoin) is only loaded and initialized one time, and that data can be cached in memory from request to request, enhancing the performance of MoinMoin.

Another advantage is that this is all based on Python.

First do ../BasicInstallation and ../WikiInstanceCreation.

Install Twisted

First, install Twisted (see URL above). Many Linux distributions have Twisted packages. Please refer to the documentation of Twisted how to install it.

Configuring the Twisted server

Copy the file wiki/server/mointwisted.py to your wiki directory. Edit and adapt the settings to your needs.

System path configuration

If you did a standard install, and you are not a developer, you probably want to skip this section. If not, you might want to add the path to moin and config file, like that:

sys.path.append('/path/to/moin')
sys.path.append('/path/to/wikiconfig')

Config class options

If you did a standard install, the default options might be just what you need. Check and change what you like:

Configuring wikiconfig.py

The sample config file should be just fine.

Starting the server on Unix

On GNU/Linux, Mac OS X or other posix like OS, copy wiki/server/mointwisted to your wiki directory. You might want to adapt the python path and the path to twistd.

Start the server with ./mointwisted start and test your wiki at http://localhost:8080/. Stop the server with ./mointwisted stop.

Starting the server on Windows

Copy wiki/server/mointwisted.cmd to your wiki directory. You might have to change the path pointing to the python-scripts directory.

Double click mointwisted.cmd to start the server. It will create a new terminal window. To stop the server, close the terminal window.

Installing and configuring standalone server for a personal wiki

The standalone server is especially made for local wikis because it does not need a web server installed. Only Python and Moin are necessary!

First do ../BasicInstallation and ../WikiInstanceCreation (home dir setup). Then copy moin.py to your wiki directory, where your wikiconfig.py is.

Configuring moin.py

System path configuration

If you did a standard install, and you are not a developer, you probably want to skip this section. If not, you might want to add the path to moin and config file, like that:

import sys
sys.path.append('/path/to/moin')
sys.path.append('/path/to/wikiconfig')

Config class options

If you did a standard install, the default options might be just what you need. Check and change what you like:

Configuring wikiconfig.py

The sample config file should be just fine.

Starting the server

Run moin.py from the command line:

$ ./moin.py
Serving on localhost:8000, documents in '/usr/share/moin/wiki/htdocs'

Test your wiki at http://localhost:8000/

To stop the server, interrupt it with Control + C.

On Windows, you can double click moin.py to start the server. A new terminal window will be opened. Close the window to stop the server.

Serving port 80 on Unix

On GNU/Linux, Mac OS X or other Posix like OS, you can serve the standard port 80 used for web serving, but you must run as root for this.

Set port to 80, and verify that user and group exists on your system. If not, set them to an existing user, meant for web serving. If needed, chown your wiki dir to this user and group.

Run moin.py as root:

$ sudo moin.py
Password:
Running as uid/gid 70/70
Serving on localhost:80, documents in '/usr/share/moin/wiki/htdocs'

Test your wiki at http://localhost/

This is pre-1.3 stuff that still has to be adapted to 1.3.

Installing MoinMoin on OS X

You must not be afraid to use the terminal. It is possible but much harder to install without the using the terminal.

There are 2 step in the installation:

1. Install the MoinMoin engine - once

2. Create wiki instance. You can create and serve as many wikis as you like.

Download

Download the source on the Desktop. You should see a moin-x.x.tar.gz file. Extract this file on the desktop with Stuffit Expander, or from the terminal (faster and safer):

cd ~/Desktop
tar -xzf moin-1.3.tar.gz

Install

Use these commands in the terminal to install the !MoinMoin wiki engine into the system.

First, open a shell as root. You will need this to install MoinMoin and configure the wiki. When asked, enter your password.

sudo -s
... password:

Now you have root privileges in this shell.

Install:

cd moin-1.3
python setup.py install --install-data='/usr'  --record=install.log 

• The --install-data='/usr' will put the shared data in the convinient '/usr/share/moin' directory. If you don't use it, your shared data will be at '/System/Library/Frameworks/Python.framework/Versions/2.3/share/moin'.

Now installation is finished. You will find a file install.log on the Desktop in the folder moin-1.3.

Creating a wiki

After you installed the software, you create a wiki. You may create several wikis if you need.

First check what is the user and group name of the web server. The wiki files will belong to the web server (not to you):

egrep "^User|^Group" /etc/httpd/httpd.conf
User www
Group www

You wil use these name soon...

Now create a copy of the default wiki:

cd /usr/share/moin
mkdir mywiki
cp -r data mywiki
cp cgi-bin/* mywiki
chown -R www:www mywiki
chmod a+rx mywiki/*.cgi

Configure Apache. We'll use the pico editor:

pico /etc/httpd/httpd.conf

Go the end of the Aliasess section and edit like the example below:

    Alias /wiki/ "/usr/share/moin/htdocs/"      
    ScriptAlias /mywiki "/usr/share/moin/mywiki/moin.cgi"       

Use Control+O to save the file and Control+X to exit pico.

Restart Apache - open System Preferences, go to the Sharing page, select "Personal Web Sharing" and click "Stop" then "Start". Or just type this instead:

apachectl graceful
... /usr/sbin/apachectl graceful: httpd gracefully restarted

Installation finished - exit from the shell with the root privileges - working as root is dangerous.

exit

Now you are running again safely.

Testing

In a web-browser surf to the site: http://localhost/mywiki

You should see the !FrontPage of your new wiki.

Now run the unit tests, to make sure everything is fine. Go to this address: http://localhost/mywiki?action=test

You should see a report on the wiki and tests results for the MoinMoin engine. If some of the tests fail, please report the problem on MoinMoinBugs.

Comments

Here are a couple of issues with my Mac OS X install I needed to fix:

1. The RSS feed for your RecentChanges page may be broken. You need to install the most recent version of PyXML. Here's how I did so and the RSS feed was fixed.
   curl -O http://aleron.dl.sourceforge.net/sourceforge/pyxml/PyXML-0.8.3.tar.gz
   tar xzvf PyXML-0.8.3.tar.gz
   cd PyXML-0.8.3
   sudo python setup.py --without-xpath build
   sudo python setup.py install

Index

1. Requirements
2. Preparation
   1. MSI Installer
   2. Installing Apache
   3. Installing Python
3. Installing MoinMoin
4. Creating a Wiki Instance
5. Integrating MoinMoin into Apache
6. Troubleshooting
   1. Internal Server Error
   2. Not Found
   3. The Page Cannot be found
   4. FrontPage Loads Without Icons

Requirements

Before you install MoinMoin, you must have the necessary infrastructure in place. This procedure explains the steps necessary to install the infrastructure and provides detailed instructions for the installation of MoinMoin.

Downloading and installing all of the required components will require almost 100 MB of disk space - shouldn't be a problem nowadays, right?

Many users prefer to install software products in a folder other than the installation default. Python typically changes the default installation folder name with each point release, and Apache has changed the default installation folder name with the release of version 2. Instead of enumerating all the possibilities at each step, this procedure will use the Reference name in the table below as the installed location for each product. Substitute your real installation location when editing configuration files and entering commands.

This installation procedure was tested with Apache 1.3.26 and Apache 2.0.44 for Windows running on Windows ME, and using Python 2.2.2 and 2.3.

Preparation

MSI Installer

Installation of Apache and one alternative distribution of Python require the Microsoft MSI Installer. The latest version, 2.0, was released in September of 2001. You will know you don't have the correct version if you receive errors after double-clicking on a file name ending in .msi. To get the latest version, go to http://www.microsoft.com/, search for msi installer, and follow the instructions. There are two versions, one for Windows ME, 98, and 95; and another for Windows 2000 and NT. Windows XP has the 2.0 version and requires no update.

Installing Apache

To obtain the latest version of Apache, go to http://www.apache.org/, and click on the link to HTTP Server. Find the link to download the Win32 Binary (MSI Installer) version. Read the Apache documentation to determine the correct installation procedure for your situation. Questions and problems with the Apache installation process should be resolved through use of the resources provided by the Apache organization. Be sure your webserver runs correctly before proceeding.

Warning: the procedure described above tends to trivialize the installation of the Apache web server. Apache can be installed and running on your PC in a very few minutes with only a cursory examination of the Apache documentation. Before you undertake the installation of any web server that can be accessed through the internet, you should exercise a controlled level of paranoia and assess the potential damage that may be caused by hackers accessing or destroying sensitive data. This should include not only the all data which resides on the PC which will host the Apache web server, but all other PCs on the local LAN which participate in any form of file sharing.

Windows ME, 98SE, 98, 95, and probably NT should be considered inappropriate hosts for any Apache web server that can be accessed via the internet. Use either Windows 2000 or XP and install all security patches available for your operating system.

Do not let the above discourage you from installing MoinMoin. Most of the internet activity probing your system for weaknesses will be from virus infected Windows NT systems running IIS whose owners have neglected to apply available security patches. The starting Apache configuration is secure and you will not have a problem provided you:

• Regularly review and apply security patches for your installed software.

• Understand the ramifications of any changes you make to the Apache config files.

• Regularly review the Apache logs for suspicious activity.

• Regularly take backups of your data.

Installing Python

There are currently two different distributions of Python available for Windows. The normal Python distribution is available from http://www.python.org. This is distributed as a windows executable (.exe) file.

An alternative distribution called ActivePython is available from http://www.activestate.com/. This distribution uses the MSI Installer and contains some tools specific to the Windows operating system and a popular Windows IDE called Pythonwin. ActivePython is available for free; an email address is requested (but not required) before downloading.

MoinMoin will work with either distribution, but requires Python release 2.2.2 or later. Download and install the distribution of your choice. Questions and problems dealing with the Python installation process should be resolved through the use of resources provided by Python.org or ActiveState. Be sure your Python installation is correct before proceeding.

Installing MoinMoin

Download the current version of MoinMoin from http://moinmoin.wikiwikiweb.de/ into C:\TEMP or an alternative location. For the .tar.gz format try WinZip.

You should then have a folder C:\TEMP\moin-x.x where "x.x" is the current release number. This folder will contain a setup.py file in addition to several other files and subfolders.

Open an MS-DOS or console window and enter the commands:

C:
cd \TEMP\moin-x.x
C:\Python\python setup.py install --record=install.log

The above commands will add MoinMoin to your C:\Python installation and create an install.log file in C:\temp\moin-x.x listing all the copied files. You may use Windows Explorer to examine the newly created folders within C:\Python. You should find a C:\Python\share\moin folder. With Python 2.2 and later it will be C:\Python\Lib\site-packages\MoinMoin. The MoinMoin folder contains many Python scripts and several subfolders.

You are now ready to create a wiki instance.

Creating a Wiki Instance

It is a good practice to try to keep all of your personal or site specific data under a few root folders. This way you can easily backup your important data on a regular basis without having to waste time either backing up static files or picking out dozens of important folders scattered throughout your folder structure. You should avoid placing your wiki data under the C:\Python folder so that you can later upgrade Python or MoinMoin without accidentally overwriting or deleting your wiki data. For the same reason, you probably don't want to place your wiki data within the C:\Apache folder. The default personal folder under many Windows versions is called C:\My Documents.

Choose a location appropriate for you; the following instructions assume you will be creating one or more wiki instances in C:\Moin\ and the first wiki instance will be named mywiki.

You may replace the name mywiki with almost any name you wish, but do not use wiki because that is used by MoinMoin for loading standard images and style sheets. Although this can be changed later, the plan is that the name you choose for mywiki will become part of the url used to access your site, e.g. http://myorganization.org/mywiki/FrontPage.

Start an MS-DOS or console window and enter the commands below. This will create a clone of the MoinMoin wiki in the mywiki folder.

cd C:\ 
md Moin
md Moin\mywiki
md Moin\mywiki\data
md Moin\mywiki\underlay
cd \Python\share\moin
xcopy data        C:\Moin\mywiki\data /E
xcopy underlay    C:\Moin\mywiki\underlay /E
copy  config\*.* C:\Moin\mywiki\*.*
copy  server\*.* C:\Moin\mywiki\*.*

If your server is going to run multiple wikis, you need to create additional clones. Do the same commands again, but use mywiki2 instead of mywiki.

Edit C:\Moin\mywiki\wikiconfig.py and at least change sitename to the name of your wiki:

sitename = 'My Wiki'

For a personal or intranet installation, you'll normally also add this line to wikiconfig.py:

allowed_actions = ['DeletePage', 'AttachFile', 'RenamePage', ]

Additional configuration details can be found in HelpOnConfiguration.

Integrating MoinMoin into Apache

Use your editor to edit the file C:\Moin\mywiki\moin.cgi. Change the first line (the shebang statement) to point to your local Python executable program. Note the forward slashes -- Apache uses the Unix convention for folder separators. This tells Apache the moin.cgi file is an executable script that will be interpreted by a program to be loaded from C:/Python/python.

#! C:/Python/python

After that, you may need to activate the lines which add a folder to the sys.path and enter your path to MoinMoin there if you have not installed MoinMoin to the site-packages dir:

   1 import sys
   2 sys.path.append(r'C:\Moin\...')

The next step is to tell Apache that is has more work to do. Use your editor to append the following lines to C:\Apache\conf\httpd.conf. Note the presence and absence of trailing slashes, it is important to enter the lines exactly as shown below.

Alias       /wiki/     "C:/Python/share/moin/htdocs/"
ScriptAlias /mywiki    "C:/Moin/mywiki/moin.cgi"

The Alias lines for wiki above instructs Apache to serve images, style sheets, etc. from the specified folders and subfolders. The ScriptAlias line is needed once for each wiki instance, so if you have multiple wikis, repeat the statement using mywiki2, mywiki3, etc. The ScriptAlias statement instructs Apache to execute scripts from the specified folder. See the Apache docs for a complete explanation.

Test your changes by restarting your Apache server and try to access your newborn wiki with the URL http://127.0.0.1/mywiki. You should see the FrontPage, try to edit and save it, and if that works, verify your edit is reflected on the RecentChanges page.

And now, it is up to you and your user community to transform your wiki into an informative and useful tool. You will probably want to retain most of the HelpOn~ pages dealing with editing, delete those pages with irrelevant information (like this page, don't let your users or boss know how easy it was to install MoinMoin ), and rewrite the FrontPage to introduce your wiki topic.

Troubleshooting

The first place to look for clues when the unexpected happens is to try changing your url to: http://127.0.0.1/mywiki?action=test. If Apache can find and execute the module C:/Moin/mywiki/moin.cgi, a page of diagnostics titled MoinMoin CGI Diagnosis will be displayed. Check the output for error messages.

The second place to look for is C:\Apache\logs\error.log. The following are common errors grouped by the message displayed by your browser.

Internal Server Error

If the Apache log shows a message "The system cannot find the file specified." then a possibility is the shebang statement in moin.cgi is incorrect.

If the Apache log shows a different error message, then the MoinMoin Python scripts may be abending. To determine the cause, you could try temporarily renaming moin.cgi to moin.py, loading moin.py with the Python idle IDE and executing it to determine if there are any error messages.

Not Found

If the Apache error log shows the message "File does not exist: C:/Apache/htdocs/mywiki", the ScriptAlias statement in httpd.conf may be incorrect.

The Page Cannot be found

If the Apache error log shows the message "File does not exist: C:/Apache/htdocs/????", you may have mistyped the url " http://127.0.0.1/mywiki" into your browser.

FrontPage Loads Without Icons

If the Apache Error log shows many error messages "File does not exist: C:/Apache/htdocs/wiki", then the Alias statement in httpd.conf may be incorrect.

This is pre-1.3 stuff that still has to be adapted to 1.3. If nobody feels like having to update it, this instructions will be deleted soon.

Index

1. Requirements
2. Preparation
   1. Installing IIS
   2. Installing Python
   3. Installing MoinMoin
3. Creating a Wiki Instance
   1. IIS 6.0 (Windows.NET Server 2003)
   2. Troubleshooting

Requirements

Before you install MoinMoin, make sure you have the necessary infra-structure in place, namely the Internet Information Services webserver (any version should be OK), and a Python installation (version 2.2.2 is required, 2.3 or higher is recommended).

In the following description, we assume that you have installed or will install things to these locations:

• IIS to its default location

• C:\Python - the Python interpreter

• C:\Moin - MoinMoin itself

Quite often, you might want to install things elsewhere, which is no problem at all; you just have to adapt any paths that appear in a command or config file to the locations you have chosen.

This installation procedure was tested with IIS 5 for Windows running on Windows 2000sp2, and using Python 2.2.2.

Preparation

Installing IIS

You currently need an external webserver to run MoinMoin.

From Microsoft: ( http://www.microsoft.com/windows2000/en/server/iis/)

• To install IIS, add components, or remove components:

  Click Start, point to Settings, click Control Panel and start the Add/Remove Programs application. Select Configure Windows, click the Components button, and then follow the on-screen instructions to install, remove, or add components to IIS.

Make sure that your webserver runs without problems before you start to install MoinMoin; problems with your webserver installation are not in the scope of this document.

Installing Python

Download Python 2.3.4 and install it. Python installation is done via a standard Windows installer program.

Installing MoinMoin

Before creating a wiki instance, you have to download and install the basic MoinMoin software. We assume you already have downloaded the distribution archive to the "C:\TEMP" directory.

Open a console window and enter the following commands:

C:
cd \temp
unzip moin-1.3.zip
cd moin-1.3
python setup.py install --prefix=C:\Moin --record=install.log

This will install all necessary files to the "C:\Moin" directory, and create a "install.log" file listing all the files that are created there.

Creating a Wiki Instance

Enter these commands in a console window:

cd \Moin
md mywiki
md mywiki\data
md mywiki\underlay
xcopy share\moin\data mywiki\data /E
xcopy share\moin\underlay mywiki\underlay /E
copy share\moin\server\moin.cgi mywiki\
copy share\moin\htdocs\index.html mywiki\default.htm

"mywiki" is the name of your wiki instance, you might want to chose a different name best fitting the intended use of this instance; just don't name it simply "wiki", because that would result in confusion and problems later on.

We have to make sure that moin.cgi can find the MoinMoin directory, so that "import MoinMoin" will work. The easiest way to make sure MoinMoin can be imported is to append to sys.path within moin.cgi.

You can change the first two lines of code in moin.cgi to something like this:

   1 #!python
   2 import sys
   3 sys.path.append(r'C:\Moin\Lib\site-packages')

Notice that we're pointing to the directory which contains the MoinMoin directory, not the directory itself.

Next, you'll need to create two virtual directories in IIS. One for the shared data, and one for this specific wiki instance.

Go to Control Panel => Administrative Tools => Internet Information Service. Open up the tree to Default Web Site.

Right click on Default Web Site and choose New => Virtual directory. This will bring up a wizard with the manditory useless first screen, hit next. Enter "wiki" for the alias name and hit next. Browse to "C:\Moin\share\moin\htdocs" and hit next. Leave the Access permissions at their defaults and hit next. And now you're done, hit finish!

Now follow the same steps, but set the alias to "mywiki" and the path to "C:\Moin\mywiki".

Use IIS Admin to remove permissions to read the data directory: expand the "mywiki" node, right click on data, select Properties, and uncheck Read. Repeat these steps with the underlay directory.

Now you need to setup the 'mywiki' alias so that it will run Python to interpret .cgi files. Right click on your new 'mywiki' alias and choose Properties. On the first tab (Virtual Directory), click the Configuration button. The first tab is the App Mappings tab, which defines which programs to use for each file exetension. Click Add. Browse to your python.exe (probably something like c:\pythonXX\python.exe). Then add -u %s %s after the Python executable path. The Executable line will look something like this: C:\Python22\python.exe -u %s %s. In the Extension box enter .cgi with the begining period. Confirm that the Check that file exists option is not checked (if it is, MoinMoin won't be able to display sub pages). Ok, you're done with the alias configuration, click OK several times to get back out of all the dialog boxes.

If you add another wiki instance, you'll only need to setup the reference to its folder, they can safely share the "wiki" alias which points to static files only.

That is all, try to access your new-born wiki with the URL "http://127.0.0.1/mywiki/". You should see the FrontPage, try to edit and save it, and if that works, see if your edit is reflected on the RecentChanges page.

Finally, edit "wikiconfig.py" and at least change "sitename" and "logo_url" to some personal values:

sitename = 'My Wiki'
logo_url = '/images/mywiki-logo.gif'

For a personal or intranet installation, you'll normally also add the line

allowed_actions = ['DeletePage', 'AttachFile', 'RenamePage', ]

IIS 6.0 (Windows.NET Server 2003)

The instructions below also apply to IIS 6.0 but the more aggressive security settings in newer version of IIS disallow the usage of unknown CGI extensions. That means you will always get a 404 error unless you do this:

1. Open "Internet Information Services (IIS)" in the control panel.

2. Go the the "Web Service Extensions" folder.

3. There you will see "All Unknown CGI Extensions" is probably set to "Prohibited". Make it "Allowed" and MoinMoin should now work.

At the time I'm writing this, I'm running Windows.NET Standard Server 2003 _RC1_. It may be different in later version. But if you get a 404 error on moin.cgi after following the regular steps, double-check that setting.

Enabling "All Unknown CGI Extensions" can be a security hole. To just enable Python CGI scripts, add and enable a new web service extension where the 'required files' exactly match the path plus arguments as described above (e.g. C:\Python23\python.exe -u %s %s). You cannot have any spaces in the path to python.exe. There are also permission issues related to the user executing the moinmoin code (access to cmd.exe) which I have not yet sorted through. -- mb

Troubleshooting

If you see an error like "ImportError: No module named MoinMoin", it means that python cannot find MoinMoin. See above for how to add to sys.path.

If you see an error like Error 13: Permission Denied, it means that your web user permissions for the files do not have write/modify enabled.

Built-in test

There's a built-in diagnostic mode that's useful when doing an install; just append "?action=test" to the URL of your wiki:

lynx --dump http://`hostname`/mywiki?action=test

If you see an import error here, but "python -c "import MoinMoin"" works, it's likely a result of missing file permissions or a wrong PYTHONPATH setting within the web server environment.

Duelling Pythons

The most common problem you might encounter is when you have an old Python version installed into "/usr", and a newer Python distribution into "/usr/local"; this is typical for GNU/Linux distributions that still come bundled with an old Python version.

In that case, if you enter "python" on your prompt, you will usually get the more recent Python interpreter, because "/usr/local/bin" is in your PATH. The situation is different in your webserver environment, and thus you might have to change the bang path of "moin.cgi", like this:

#!/usr/local/bin/python

"""
    MoinMoin - CGI Driver Script
...
"""

Missing file permissions

If you are root, the installed files may be readable only by root, but they must also be readable by the web server before the wiki will work. This includes both the Python modules and the site itself. For the data directory, the wiki engine also needs write access. To fix this, first find out where the Python module directory is; look in install.log, or run the command:

python -c "import sys; print '%s/lib/python%s/site-packages' % ( sys.prefix, sys.version[:3] )"

For the example below, we'll assume that the Python module directory is /usr/local/lib/python2.3/site-packages. Make the files world-readable using the following commands:

cd /usr/local
chmod -R a+rX lib/python2.3/site-packages/MoinMoin