DokuWiki Installer


This page assists in the first time installation and configuration of Dokuwiki. More info on this installer is available on it's own documentation page.

DokuWiki uses ordinary files for the storage of wiki pages and other information associated with those pages (e.g. images, search indexes, old revisions, etc). In order to operate successfully DokuWiki must have write access to the directories that hold those files. This installer is not capable of setting up directory permissions. That normally needs to be done directly on a command shell or if you are using hosting, through FTP or your hosting control panel (e.g. cPanel).

This installer will setup your DokuWiki configuration for ACL, which in turn allows administrator login and access to DokuWiki's admin menu for installing plugins, managing users, managing access to wiki pages and alteration of configuration settings. It isn't required for DokuWiki to operate, however it will make Dokuwiki easier to administer.

Experienced users or users with special setup requirements should use these links for details concerning installation instructions and configuration settings.

For security reasons this script will only work with a new and unmodified Dokuwiki installation. You should either re-extract the files from the downloaded package or consult the complete Dokuwiki installation instructions

driven by DokuWiki powered by PHP
MantisBT Build Process proposal [Mantis Bug Tracker Wiki]

User Tools

Site Tools


MantisBT Build Process proposal

This page is only a draft, pending discussion on the development mailing list.


This document proposes a number of improvements to the MantisBT build process, by introducing a structured build process used to validate code changes as they happen and to produce nightly builds.


  • Increased visibility of the build results and of their consumability
  • Increased feedback speed regarding corectness of changes
  • Larger testing coverage of the MantisBT codebase


  • Continuous deployment of the resulting artifacts
  • Generating release artifacts , replacing the current release process

Build process

The current MantisBT testing infrastructure supports two kinds of tests:

  • Self-contained unit tests
  • Integration tests for the SOAP API

These tests could be arranged in the following succession

  1. Unit tests
  2. Integration tests SOAP matrix build
    1. Integration tests running against MySQL Community 5.1.x
    2. Integration tests running PostgreSQL 9.0.x

Database backend extensibility

This build will allows us to easily scale in the medium term by adding more databases from those in our supported or experimental phase:

  1. DB2 Express 9.7.x
  2. Oracle XE 10g
  3. SQL Server Express ( problematic, probably requires Windows license )

Adding new kinds of integration tests

As we progress, we will be able to new kinds of matrix builds, for instance:

  1. file API builds against multiple backends ( database, file, ftp )
  2. authentication API builds against different authentication schems ( Mantis internal, LDAP )

Another possibility is to add Selenium-driven tests to our build, to validate that the pages work as expected .

Publishing results

The results will be published as checksummed archives, which have a validated quality - they pass ( or not ) the tests as currently defined. This is key information for both developers and early consumers of the build and encourages rapid feedback on versions still in development.

mantisbt/build_process.txt · Last modified: 2011/11/18 09:18 by rombert