How to upgrade mediawiki - Revision history

Srevilak: /* Update composer dependencies */

2019-08-10T15:44:08Z

Update composer dependencies

← Older revision		Revision as of 11:44, 10 August 2019
Line 72:		Line 72:
	== Update composer dependencies ==		== Update composer dependencies ==

	$ ~/bin/composer update		$ ~/bin/composer.phar self-update
			$ ~/bin/composer.phar update

			Note: if composer is too old, it may be necessary to remove and reinstall it.

	== Running Maintainance Scripts ==		== Running Maintainance Scripts ==

Srevilak: /* The Upgrade Process */ Notes on mediawiki skin updates

2019-08-10T15:42:58Z

The Upgrade Process: Notes on mediawiki skin updates

@@ Line 36: / Line 36: @@
 # update composer's dependencies
 # run maintenance/update.php
-# resolve any changes to configuration variables.
+# resolve any changes to configuration variables
 We'll go through these steps one at a time
@@ Line 82: / Line 83: @@
 mediawiki's root directory.  It's a good idea to look through these
 files anyway, to see what changes are in the new release.

Srevilak: Notes on mediawiki branch management during upgrades

2019-08-10T15:33:43Z

Notes on mediawiki branch management during upgrades

← Older revision		Revision as of 11:33, 10 August 2019
Line 63:		Line 63:
	=== Switching to a new Release branch ===		=== Switching to a new Release branch ===

	~~''(to be written)''~~		The general gist

	~~== Running Maintainance Scripts ==~~		# identify changes you've made on the current branch
			# create a local branch, to mirror one of the mediawiki release branch
	~~$ php maintenance/update~~.~~php~~		# cherry pick local changes made on the old branch.

	== Update composer dependencies ==		== Update composer dependencies ==

	$ ~/bin/composer update		$ ~/bin/composer update

			== Running Maintainance Scripts ==

			$ php maintenance/update.php

	== Resolving Changes to Configuration Variables ==		== Resolving Changes to Configuration Variables ==

Srevilak: /* The Upgrade Process */ composer must be updated before running update.php, because update.php depends on file that came from Compower

2019-08-10T15:31:20Z

The Upgrade Process: composer must be updated before running update.php, because update.php depends on file that came from Compower

← Older revision		Revision as of 11:31, 10 August 2019
Line 34:		Line 34:
	# Backup the database		# Backup the database
	# upgrade code		# upgrade code
			# update composer's dependencies
	# run maintenance/update.php		# run maintenance/update.php
	~~# update composer's dependencies~~
	# resolve any changes to configuration variables.		# resolve any changes to configuration variables.

Srevilak: changed headings

2016-12-10T20:21:54Z

changed headings

← Older revision		Revision as of 16:21, 10 December 2016
Line 1:		Line 1:
			= Background =

	Our wiki installation is cloned from mediawiki's git repository.		Our wiki installation is cloned from mediawiki's git repository.
	Mediawiki has branches for each release; we have branches that track		Mediawiki has branches for each release; we have branches that track
Line 26:		Line 28:
	That's the overview. I'll go into more detail below.		That's the overview. I'll go into more detail below.

	= ~~General~~ Process =		= The Upgrade Process =

	With that said, the upgrade involves five steps.		With that said, the upgrade involves five steps.

Srevilak: initial revision

2016-12-10T20:20:58Z

initial revision

New page

Our wiki installation is cloned from mediawiki's git repository.
Mediawiki has branches for each release; we have branches that track
mediawiki branches.

In general, the Masspirates mediawiki is the standard mediawiki
distribution, plus a couple of commits (for changes to
LocalSettings.php and such).

For example:

$ git status
On branch mapp-1.28
Your branch is ahead of 'origin/REL1_28' by 2 commits.
(use "git push" to publish your local commits)

$ git branch
* mapp-1.28
master

Above, mapp-1.28 is based on mediawiki's REL1_28 branch, and there are a
few changes on top. Upgrading follows one of two procedures:

# Pulling in changes from the same branch. In this case, just rebase
# Switching to a new branch. Here, we want to make a new (local) branch off the new upstream release, and cherry pick

That's the overview. I'll go into more detail below.

= General Process =

With that said, the upgrade involves five steps.

# Backup the database
# upgrade code
# run maintenance/update.php
# update composer's dependencies
# resolve any changes to configuration variables.

We'll go through these steps one at a time

== Database Backup ==

mysqldump --verbose -uUSER -pPASSWD --complete-insert=1 DBNAME | gzip -9 > masspira_mdw1.$(date +%F).sql.gz
mv *.sql.gz backup

== Update Code ==

=== Rebasing from the same branch ===

git status # should be no outstanding changes
git remote update
git rebase origin/REL1_28

Above, substitute "origin/REL1_28" with the actual upstream branch.

Having done this,

git log --oneline origin/REL1_28..HEAD

lists the local changes we've made.

=== Switching to a new Release branch ===

''(to be written)''

== Running Maintainance Scripts ==

$ php maintenance/update.php

== Update composer dependencies ==

$ ~/bin/composer update

== Resolving Changes to Configuration Variables ==

For this step, look at the "UPGRADE" and "RELEASE-NOTES" files in
mediawiki's root directory. It's a good idea to look through these
files anyway, to see what changes are in the new release.