Renamed project, mediawiki lost (Previous 7.3) Ĭorresponds and fixed by request #6630 Mediawiki db not renamed when project unixname is renamed You will be able to re-trigger the global This will gracefully stop the SystemEvent execution after the current migration. I would like to do that in Mediawiki with the math extensions.
Main SystemEvents queue), you can stop the execution by creating a file /var/tmp/tuleap_cache/STOP_SYSTEM_EVENT. I need to solve a complicated math equation that I will have to show to people and ask. If you have a very long list of projects to migrate and the event it taking too long (it will block the execution of You can also migrateĪll projects at once with the dedicated toggle. In Site Admin “Mediawiki” section, there is a panel to select the projects you want to migrate.
#MEDIAWIKI MATH UPGRADE#
Since Tuleap 9.13, mediawiki 1.23 is installed by default and it’s strongly recommended to upgrade all projects to Activate the Math extension Ĭan be activated on your instance by installing the package mediawiki-math-tuleap. It’s recommended to purge the databases (see previous section) prior to migrate to central database. Use project_id to migrate one project after another (during testing phase). This will queue a System Event that will do the heavy work, check the System Event console for status. $> /usr/share/tuleap/plugins/mediawiki/bin/move_to_single_db.php Projects can re-activate mediawiki service in the future. It’s possible to force delete of those empty mediawiki by explicitly adding the corresponding project number on command line. Identify all projects with mediawiki service activated but without content In both cases, there is no problems to re-activate an (empty) mediawiki in those projects in the future. It’s possible to force removal by explicitly adding the corresponding project number on command line. If the service is unused and mediawiki has some content, a warning is issued. Clean-up tables and databases ĭelete all databases that are left after a project deletion (before 9.13, mediawiki databases were not deleted on project deletion).ĭelete all databases that are empty in projects that don’t use mediawiki service. Un-used mediawiki and eventually purge them. It’s recommended to not enable mediawiki by default in project templates and regularly run the clean-up tool to identify If you have 100 projects using mediawiki, they will eat 5100 tables. One mediawiki database corresponds to 51 tables (as of mediawiki 1.23) so In order to achieve this, you need to have 1 set of table per wiki (either in a dedicated database or Wiki Farm is a trick that allow to serve different wiki on top of the The last point is really important to understand. We rely on Wiki Farm mecanism to provide one mediawiki per project. Some extensions are bundled by default, see Mediawiki section in User Guide. Tuleap relies on external mediawiki package wrapped with a Tuleap Skin. As a site administrator you should be aware that
0 kommentar(er)
