Opened 3 years ago

Closed 3 months ago

Last modified 3 months ago

#2004 closed task (fixed)

Wiki rebuild

Reported by: Jeff McKenna Owned by: sac@…
Priority: major Milestone: Sysadmin Contract 2020-I
Component: Wiki Keywords:
Cc: Jeff McKenna

Description

Change History (16)

comment:1 Changed 3 years ago by strk

Would it be too risky to also try migrating from MySQL to PostgreSQL ? https://www.mediawiki.org/wiki/Manual:PostgreSQL

comment:2 Changed 3 years ago by martin

https://www.mediawiki.org/wiki/Release_notes/1.29#Compatibility says:

"MediaWiki? 1.29 requires PHP 5.5.9 or later."

The Wiki VM is running on Debian6 which has PHP 5.3.3.1. Thus, upgrading MediaWiki? requires upgrading the OS beforehand, Debian8 would be minimum. Given the fact that upgrading the OSGeo VM's just to Debian7 is pretty tricky - due to the disk layout they probably refuse to boot afterwards - I wonder, wether it's worth the trouble. Of course we can move the entire Wiki to Osgeo6 or some other VM/machine.

Suggestions, opinions ?

Aside from that, personally I'd be very much in favour of away from MySQL ....

comment:3 Changed 3 years ago by robe

Away from MySQL sounds good to me though do we know if there is anything we are using not supported in the PostgreSQL support. Sounds like MySQL is still more battery tested.

comment:4 Changed 3 years ago by christian

I would not go for PostgreSQL, almost no MW Extensions support PostreSQL as well as MySQL/MariaDB. You will certainly have more trouble maintaining a PostgreSQL based MW with Extensions compared to a MariaDB/MySQL.

And for Semantic MW the PostgreSQL support seems to be broken:

*https://www.semantic-mediawiki.org/wiki/PostgreSQL

*https://phabricator.wikimedia.org/T44659

comment:5 Changed 3 years ago by msmitherdc

This is just a comment so feel free to ignore but perhaps it might be time to think about dockerization (or insert your favorite container solution) so that all the dependencies can be kept together and not impact other operations.

comment:6 Changed 3 years ago by Jeff McKenna

I always use the recommended backend for trac/mediawiki/joomla/wordpress/plone. In this case MySQL has served us well for the wiki. I'm very familiar with maintaining these backends, so MySQL is not an issue. +1 to keep same backend.

comment:7 Changed 3 years ago by robe

Sounds like it's not worth switching without some serious testing. Oh well I'm okay with a MariaDb?/MySQL solution then. Preferably MariaDb?.

comment:8 Changed 2 years ago by strk

More reasons to upgrade are written in #1819, which I'm closing in favour of this newer one.

comment:9 Changed 15 months ago by robe

Milestone: Sysadmin Contract 2019-I
Summary: Upgrade MediaWiki versionWiki rebuild

I'm proposing a complete rebuild

Debian (9 or 10 depending on when we get to it) MariaDb? PHP 7 (right now it's at an EOL'd PHP 5.4 as I recall) Apache (or should we go with nginx)?

and make it an lxd container

comment:10 Changed 14 months ago by robe

Milestone: Sysadmin Contract 2019-ISysadmin Contract 2019-II

Moving this to contract 2

comment:11 Changed 5 months ago by robe

Milestone: Sysadmin Contract 2019-IISysadmin Contract 2020-I

comment:12 Changed 5 months ago by robe

I've started a new container on osgeo3 called wiki-new. Additional note this is running debian10 with osgeo ldap/ssh

Currently have apache2, mariadb, and PHP 7.3 on in and now in middle of the apache configs

I'm going to see if I run into stumbling blocks copying over the old wiki db/data and upgrading it.

Last edited 5 months ago by robe (previous) (diff)

comment:13 Changed 4 months ago by robe

Okay I think I've made some good progress here:

You can see at https://wiki.new.osgeo.org

This is running on osgeo3 wiki-new container -- what I have done so far

1) Started with a fresh new debian 10 container with apache2/php/mariadb 2) Restored the backup (3/31/2020) and files from old-wiki container 3) Fiddled with the LocalSettings?.php and upgrade the extensions that have changed since 4) Installed https://releases.wikimedia.org/mediawiki/1.34/mediawiki-1.34.1.tar.gz which is currently latest version

5) Ran the maintenance/upgrade.php script.

Can all see if they can get it.

I know I'll have to rerun this again. But planning to look at the mysql db to see what kind of mess we are looking at to get rid of junk accounts before moving forward with LDAP.

Version 0, edited 4 months ago by robe (next)

comment:14 Changed 4 months ago by robe

okay seems I still have work to do upgrading the plugins

I just installed semanticmediawiki and going thru the other extensions listed on this page

Old Wiki

https://wiki.new.osgeo.org/wiki/Special:Version

New Wiki https://wiki.new.osgeo.org/wiki/Special:Version

Hoping to be able to salvage all with newer versions.

comment:15 Changed 3 months ago by robe

Resolution: fixed
Status: newclosed

Completed the migration so wiki.osgeo.org is back on osgeo3

and container is called wiki. Installation steps documented at - https://git.osgeo.org/gitea/sac/osgeo3/wiki/wiki-container

It is running MediaWiki? 1.34, 10.3.22-MariaDB, PHP 7.3

Detailed here - https://wiki.osgeo.org/wiki/SAC_Service_Status#wiki

comment:16 Changed 3 months ago by strk

Great work ! Now on to LDAP !

Note: See TracTickets for help on using tickets.