MediaWIKI Upgrade: Difference between revisions

Line 5:

Backup the website files (actually make a copy)<syntaxhighlight lang="text">

mv WebSiteDirectory WebSiteDirectory.~~VERSION-WORKING~~ (~~my naming convention~~)

mv WebSiteDirectory WebSiteDirectory.WorkingVersionX.YZ

...then copy to original files over the expanded upgrade files (see steps later)

</syntaxhighlight>The above is the quickest way to make an exact copy of the website files (unlike NTFS, Linux permissions are simple and will be copied with the above command) and also test as you go. IE, the copied files can be checked for functionality by going to the web site.

~~</syntaxhighlight>The above is~~ the ~~quickest way to make an exact copy of the website files (unlike NTFS~~, ~~Linux permissions are simple and will be copied with~~ the ~~above~~ command~~) and also test as you go~~. IE, ~~the copied files can be checked for functionality by going to the web site~~.

For the database, use the command line or phpMyAdmin. phpMyAdmin makes it really easy. Select the database, export, simple, Go, save it, done.

==Upgrade (Actually Install and Copy)==

Line 22:

Line 24:

find /var/www/html/WhatEverDirectory/images -type d -exec chmod 755 {} \;

</syntaxhighlight>Copy previous version of MediaWiki website files into the new directory: cp -R -n -v WhatEverSource WhatEverDestination (This will not overwrite any new files, IE "upgraded" files, but has the effect of copying all the extensions, images, and any other files from the old website version, while paying deference to the newer files.

=== LocalSettings.php ===

Copy the old copy of the LocalSettings.php file into the upgrade directory as the "new one", if it exists, wouldn't be overwritten with the new copy process. See this for a tip on the LocalSettings.php file.

===Modification of Files===

@@ Line 5: / Line 5: @@
 Backup the website files (actually make a copy)<syntaxhighlight lang="text">
-mv WebSiteDirectory WebSiteDirectory.VERSION-WORKING (my naming convention)
+mv WebSiteDirectory WebSiteDirectory.WorkingVersionX.YZ
+...then copy to original files over the expanded upgrade files (see steps later)
+</syntaxhighlight>The above is the quickest way to make an exact copy of the website files (unlike NTFS, Linux permissions are simple and will be copied with the above command) and also test as you go.  IE, the copied files can be checked for functionality by going to the web site.
-</syntaxhighlight>The above is the quickest way to make an exact copy of the website files (unlike NTFS, Linux permissions are simple and will be copied with the above command) and also test as you go.  IE, the copied files can be checked for functionality by going to the web site.
+For the database, use the command line or phpMyAdmin.  phpMyAdmin makes it really easy.  Select the database, export, simple, Go, save it, done.
 ==Upgrade (Actually Install and Copy)==
@@ Line 22: / Line 24: @@
 find /var/www/html/WhatEverDirectory/images -type d -exec chmod 755 {} \;
 </syntaxhighlight>Copy previous version of MediaWiki website files into the new directory: cp -R -n -v WhatEverSource WhatEverDestination (This will not overwrite any new files, IE "upgraded" files, but has the effect of copying all the extensions, images, and any other files from the old website version, while paying deference to the newer files.
+=== LocalSettings.php ===
+Copy the old copy of the LocalSettings.php file into the upgrade directory as the "new one", if it exists, wouldn't be overwritten with the new copy process.  See this for a tip on the LocalSettings.php file.
 ===Modification of Files===