Us copy the right extensions over: $ cd ~/htdocs Reduce typing, let’s make some symlinks for the existing (old) MediaWiki and for theĬurrent (new) MediaWiki, naming them “aa” and “bb” respectively. Mediawiki directory, yet not in our newly created one. We do want to copy any extensions that exist in our old The tarball, as they are considered “core” extensions. MediaWiki bundles a number of extensions in Now it is time to copy over the extensions. $ rm -fr images/ # Careful, make sure you are in the right directory! :) This allows for easy testing and upgrades: $ cd ~/htdocs/mediawiki-1.26.2 I keep the images directory a level up from the actual mediawikiĭirectory, and symlink it in. The tarball comes with a dummy directory containing a few unimportant files. $ cp mediawiki/Wiki_logo.png mediawiki-1.26.2/ To keep nice and visible at the top level): $ cp mediawiki/LocalSettings.php mediawiki-1.26.2/ Primary key fingerprint: 41B2 ABE8 17AD D3E5 2BDA 946F 72BC 1C5D 2310 7F8AĬopy the tarball to your server, and untar it in the same base directory as yourĬopy the LocalSettings.php file over, as well as any custom images (e.g. Gpg: There is no indication that the signature belongs to the owner. Gpg: WARNING: This key is not certified with a trusted signature! Gpg: aka "Chad Horohoe (Alias for existing email) " Gpg: aka "Chad Horohoe (Personal e-mail) " Gpg: Signature made Sun 08:13:14 PM EST using RSA key ID 23107F8A Gpg: assuming signed data in `mediawiki-1.26.2.tar.gz' Grab both the tarball (tar.gz) and the signature (.tar.gz.sig) file, then use gnupg to verify it: $ wget You can always find a prominent link on. For this example, we want the highest in the 1.26 branch, which as of this Always get the latest revision in the currentīranch. Nothing to commit, working directory clean It should look like this: $ cd ~/htdocs/mediawiki Then check you are on the main branchĪnd have no outstanding changes. Site controlled by Git, right? If not, go do so right now. Going from version 1.25.3 to 1.26.2 Preparationīefore making any changes, make sure everything is up to date in When done, run through again, but this time on the actual live site.įor this article, we will use MediaWiki installed in ~intranet/htdocs/mediawiki, and Then run through the steps below to find any problems See this article on how to make such a clone. The first step to a major MediaWiki upgrade is to try it on a cloned, test version of your wiki. Software changes, whereas a minor update (in which only the revision changes) simply To 1.26) is a larger undertaking than updating the revision, as it involves significant Moving from one major version to another (for example 1.25 Thus, version 1.26.2 is the third revision (0, then 1, then 2) of theġ.26 version of MediaWiki. Numbers combined give the major version, and the number on the end the revision of MediaWiki, like Postgres, uses a three-section version number in which the first two While the official upgrade instructions are good, they don’t cover everything. In this one, I’ll cover my solution to doing a “major” upgrade to MediaWiki. In a previous article I covered how to upgrade minor revisions of MediaWiki with patches. Keeping your MediaWiki site up to date with the latest version is, like many sysadmin tasks, a never-ending chore.
0 Comments
Leave a Reply. |