Manual:Moving a wiki/ru

На этой странице объясняется, как перенести вики-сайт на другой сервер. Это часто требуется при переходе на другой веб-сервер или домен (или то и другое одновременно).

Самый безопасный способ сделать это — использовать одну и ту же версию MediaWiki в обеих вики, старой и новой. Однако, можно установить на новый сервер более свежую версию MediaWiki и выполнить обновление непосредственно на новом сервере. На самом деле, это может оказаться для вас единственным вариантом, если вы хотите обновить свою вики до новой версии, имеющей более высокие требования, чем те, которые доступны на вашем старом сервере (как, например, версия php).

Эти шаги в основном объясняются на других страницах:


 * 1) Создайте резервную копию своей вики.
 * 2) Перенесите резервные копии со старого сервера на новый.
 * 3) Восстановите резервную копию на новом сервере.

Обновление нового сервера
If you are upgrading to a newer MediaWiki version on the new server, instead of copying the old MediaWiki directory and extensions to the new server, you should follow the upgrading procedure. You'll download a new MediaWiki version on the new server and fresh versions of the extensions you use, matching the new MediaWiki version. Remember to run the update script.

Замечания

 * If the URL has changed (for example, a new domain), be sure to update all references to it in LocalSettings.php. If using VisualEditor, you'll need to update Parsoid configuration too.
 * Links on cached pages may still point to the old domain. You may need to bump $wgCacheEpoch to discard cached pages prior to that time.
 * Check that the  directory has the correct permissions set if using uploads; it must be writable by the web server.
 * Make sure any extension directories have the correct permissions as well (e.g., if linux: )
 * When manually transferring a wiki from a windows platform to a Linux platform the best method is to:
 * 1) Manually install MediaWiki on the Linux platform from a tar file as outlined here: Manual Install of Wiki (i.e., try not to use install from an automated package)
 * 2) Replace the newly installed MediaWiki folder (e.g., /var/www/mediawiki...) on your Linux machine with the MediaWiki base folder from your windows machine
 * 3) Update your Linux machine's MySQL Database (e.g. wikidb) with the wiki database from your windows machine (i.e., use the backup and restore features of mysql as outlined above)
 * After importing a wiki database, even if the database can work, some minor problems may arise:
 * 1) You might need to repair Searchindex: In phpMyAdmin, enter "  " for rebuilding the search index. wikidb is your database's name.
 * 2) The collation of some rows may be changed. Cross-check it with the original database.

Тестирование
At this point, try to use the wiki on the new server. Log in as a sysop and a regular user and check that viewing, creating and editing pages and uploading files still works. Fix any problems reported either by PHP or MediaWiki itself.

You can do the entire process to test if the move will work without problems, before actually putting the old wiki in read-only mode. Once you know your wiki in the new server works as expected, you can put your old wiki in read-only mode and perform the move again.

Частые проблемы

 * Недоступные файлы после смены домена

The column md_deps in the module_deps table contains absolute file paths, which are used to locate the images and LESS files that CSS depends on. These paths break when the wiki is, e.g., moved to another folder or another server. After your move, you might see PHP warnings that certain files could not be accessed. In current versions of MediaWiki, this can be solved by running update.php, thus clearing caches.

In versions older than MediaWiki 1.25 (where T37472 is not implemented), update.php does not delete the contents of the module_deps table. For these versions, the workaround is to manually fix wrong entries in the module_deps table:

This can be used to update wrong path segments and to fix the error.

A similar issue can happen when MediaWiki tries to read resource loader messages. In this case the solution is to truncate the according tables:

См. также

 * - if you don't have a successful backup
 * - change the installation directory of your wiki
 * - A set of tools to transfer content from one wiki to another if you don't have shell access to the old wiki.
 * - change the installation directory of your wiki
 * - A set of tools to transfer content from one wiki to another if you don't have shell access to the old wiki.
 * - A set of tools to transfer content from one wiki to another if you don't have shell access to the old wiki.

Внешние ссылки

 * Detailed instructions on 'Migrating to a new server'
 * Specific page to move easily a wiki (in french)