Wiki name: Must not be blank or "MediaWiki" and may not contain "#"
Preferably a short word without punctuation, i.e. "Wikipedia".
Contact e-mail:
Displayed to users in some error messages, used as the return address for password reminders, and used as the default sender address of e-mail notifications.
Language:
en - English
nl - Nederlands
Select the language for your wiki's interface. Some localizations aren't fully complete. Unicode (UTF-8) is used for all localizations.
A notice, icon, and machine-readable copyright metadata will be displayed for the license you pick.
Admin username:
Password: Cannot be blank
Password confirm:
An admin can lock/delete pages, block users from editing, and do other maintenance tasks.
An object caching system such as memcached will provide a significant performance boost,
but needs to be installed. Provide the server addresses and ports in a comma-separated list.
Use this to disable all e-mail functions (password reminders, user-to-user e-mail, and e-mail notifications)
if sending mail doesn't work on your server.
The user-to-user e-mail feature (Special:Emailuser) lets the wiki act as a relay to allow users to exchange e-mail without publicly advertising their e-mail address.
For this feature to work, an e-mail address must be present for the user account, and the notification
options in the user's preferences must be enabled. Also note the
authentication option below. When testing the feature, keep in mind that your own changes will never trigger notifications to be sent to yourself.
There are additional options for fine tuning in /includes/DefaultSettings.php; copy these to your LocalSettings.php and edit them there to change them.
If this option is enabled, users have to confirm their e-mail address using a magic link sent to them whenever they set or change it, and only authenticated e-mail addresses can receive mails from other users and/or
change notification mails. Setting this option is recommended for public wikis because of potential abuse of the e-mail features above.
Database host:
If your database server isn't on your web server, enter the name or IP address here.
Database name:
DB username:
DB password: Must not be blank
DB password confirm:
If you only have a single user account and database available,
enter those here. If you have database root access (see below)
you can specify new accounts/databases to be created. This account
will not be created if it pre-exists. If this is the case, ensure that it
has SELECT, INSERT, UPDATE, and DELETE permissions on the MediaWiki database.
Superuser account:
Use superuser account
Superuser name:
Superuser password:
If the database user specified above does not exist, or does not have access to create
the database (if needed) or tables within it, please check the box and provide details
of a superuser account, such as root , which does.
MySQL specific options
Database table prefix:
If you need to share one database between multiple wikis, or
between MediaWiki and another web application, you may choose to
add a prefix to all the table names to avoid conflicts.
Avoid exotic characters; something like mw_ is good.
InnoDB is best for public web installations, since it has good concurrency
support. MyISAM may be faster in single-user installations. MyISAM databases
tend to get corrupted more often than InnoDB databases.
This option is ignored on upgrade, the same character set will be kept.
WARNING: If you use backwards-compatible UTF-8 on MySQL 4.1+, and subsequently back up the database with mysqldump , it may destroy all non-ASCII characters, irreversibly corrupting your backups!.
binary mode , MediaWiki stores UTF-8 text to the database in binary fields. This is more efficient than MySQL's UTF-8 mode, and allows you to use the full range of Unicode characters. In UTF-8 mode , MySQL will know what character set your data is in, and can present and convert it appropriately, but it won't let you store characters above the Basic Multilingual Plane .
PostgreSQL specific options
Database port:
Schema for mediawiki:
Schema for tsearch2:
The username specified above (at "DB username") will have its search path set to the above schemas,
so it is recommended that you create a new user. The above schemas are generally correct:
only change them if you are sure you need to.
SQLite specific options
NOTE: SQLite only uses the Database name setting above, the user, password and root settings are ignored.
SQLite data directory:
SQLite stores table data into files in the filesystem.
If you do not provide an explicit path, a "data" directory in
the parent of your document root will be used.
This directory must exist and be writable by the web server.
MSSQL specific options
Database table prefix:
If you need to share one database between multiple wikis, or
between MediaWiki and another web application, you may choose to
add a prefix to all the table names to avoid conflicts.
Avoid exotic characters; something like mw_ is good.
DB2 specific options
Database port:
Schema for mediawiki:
Select one:
If you need to share one database between multiple wikis, or
between MediaWiki and another web application, you may specify
a different schema to avoid conflicts.