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:db_dump_restore [Mantis Bug Tracker Wiki]

User Tools

Site Tools


mantisbt:db_dump_restore

Information originally from djcarr in bug #8407 here


After more investigation I've come up with a set of good guidelines for dumping and importing fairly large mantis databases. I'll post them here in case they can help someone else.

  • 1. In MySQL Server's my.ini set the following. This allows file attachments greater than 1MB to be imported back in.
[mysqld]
max_allowed_packet=16M
  • 2. Dump the file attachments table alone in hex format.
mysqldump --host=*** --user=*** --password=*** --hex-blob --skip-extended-insert --result-file=mantisdb_files.sql mantisdb mantis_bug_file_table

Why? Because this one table can get very big and MySQL Server cannot reimport scripts more than about 50MB. So you can then split this table dump into multiple smaller files if needed.

  • 3. Dump the remainder of the database. These options ensure one line per row, again for ease of reading and splitting the dump if needed.
mysqldump --host=*** --user=*** --password=*** --skip-extended-insert --ignore-table=mantisdb.mantis_bug_file_table --result-file=mantisdb.sql mantisdb 
  • 4. Import the files in sequence into the NEW database:
mysql --host=*** --user=*** --password=*** newmantisdb < mantisdb_files.sql
mysql --host=*** --user=*** --password=*** newmantisdb < mantisdb.sql

Do NOT use the MySQL Query Browser GUI to import - use the command line as above. The Query Browser chokes badly on the many '/ escapings that mysqldump places in the bug text and descriptions.

mantisbt/db_dump_restore.txt · Last modified: 2008/10/29 04:25 (external edit)