Hello,
I have been running Mediawiki and updating with git - general outline here: https://www.mediawiki.org/wiki/Download_from_Git#Keeping_up_to_date
On update I pull recent versions of: (1) mediawiki, (2) the extensions, (3) the skins, and (4) the external libraries with git.
I then run 'update' from the command line ( php maintenance/update.php ).
One issue I encountered is that: the extensions don't update right away - as per the page 'Special:Version'.
Is there a simple way to reload the extensions? Is it caching?
Any help/ideas on this would be appreciated!
Thanks, Michael
-- Mediawiki 1.27.3 git version 2.1.4
Prior related post - https://lists.wikimedia.org/pipermail/mediawiki-l/2016-August/045818.html
The extension diectory is its own repo, check it out and update it, along with the skins directory
On Sat, Dec 30, 2017 at 6:55 PM Dr. Michael Bonert < michael@librepathology.org> wrote:
Hello,
I have been running Mediawiki and updating with git - general outline here: https://www.mediawiki.org/wiki/Download_from_Git#Keeping_up_to_date
On update I pull recent versions of: (1) mediawiki, (2) the extensions, (3) the skins, and (4) the external libraries with git.
I then run 'update' from the command line ( php maintenance/update.php ).
One issue I encountered is that: the extensions don't update right away - as per the page 'Special:Version'.
Is there a simple way to reload the extensions? Is it caching?
Any help/ideas on this would be appreciated!
Thanks, Michael
-- Mediawiki 1.27.3 git version 2.1.4
Prior related post - https://lists.wikimedia.org/pipermail/mediawiki-l/2016-August/045818.html
MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
On Sat, Dec 30, 2017 at 5:54 PM, Dr. Michael Bonert michael@librepathology.org wrote:
One issue I encountered is that: the extensions don't update right away - as per the page 'Special:Version'.
Is there a simple way to reload the extensions? Is it caching?
Special:Verison caches the VCS version information for each extension [0]. In theory this cache will be invalidated each time the git hash of $IP is updated. It should be possible to write a maintenance script to ensure that the caches are purged for the current hash of $IP. In practice though it is only a cosmetic issue.
[0]: https://phabricator.wikimedia.org/source/mediawiki/browse/master/includes/sp...
Bryan
If you have lots of extensions; and maintain a git checkout for each extension, I wrote a script to help with upgrades: https://freephile.org/wiki/MediaWiki/Upgrade/REL1_26_to_REL1_27 The script checks each extension directory for a .git dir, the status of the current checkout, whether or not there is a compser.json and/or composer.lock file,
You might want to add a "-q" to quiet the output of *git fetch*
The script would need to be configured for the releases in mind (e.g. to upgrade REL1_28 to REL1_29), and to change it from "reporting" mode to "upgrade" mode, you must set $doUpgrade to *true.* Produces output like the following in "reporting" mode:
sudo php ./inspectExtensions.php
Directories marked with * are git controlled and decorated with their current branch matching REL1_28 AJAXPoll REL1_28 upgradable origin/REL1_29 git checkout -b REL1_29 origin/REL1_29 && composer install --no-dev AdminLinks REL1_28 upgradable origin/REL1_29 git checkout -b REL1_29 origin/REL1_29 && composer install --no-dev AntiBot REL1_28 upgradable origin/REL1_29 git checkout -b REL1_29 origin/REL1_29 AntiSpoof REL1_28 upgradable origin/REL1_29 git checkout -b REL1_29 origin/REL1_29 && composer install --no-dev ApprovedRevs master Arrays REL1_28 upgradable origin/REL1_29 git checkout -b REL1_29 origin/REL1_29 BatchUserRights REL1_28 upgradable origin/REL1_29 git checkout -b REL1_29 origin/REL1_29 BetaFeatures REL1_28 upgradable origin/REL1_29 git checkout -b REL1_29 origin/REL1_29 Bootstrap CSS REL1_28 upgradable origin/REL1_29 git checkout -b REL1_29 origin/REL1_29 CategorySuggest (detached ... ...
Greg Rundlett https://eQuality-Tech.com https://freephile.org
On Sat, Dec 30, 2017 at 9:31 PM, Bryan Davis bd808@wikimedia.org wrote:
On Sat, Dec 30, 2017 at 5:54 PM, Dr. Michael Bonert michael@librepathology.org wrote:
One issue I encountered is that: the extensions don't update right away
- as
per the page 'Special:Version'.
Is there a simple way to reload the extensions? Is it caching?
Special:Verison caches the VCS version information for each extension [0]. In theory this cache will be invalidated each time the git hash of $IP is updated. It should be possible to write a maintenance script to ensure that the caches are purged for the current hash of $IP. In practice though it is only a cosmetic issue.
master/includes/specials/SpecialVersion.php;58f37bd13c49f0e449d2373e090167 99f9e35f48$735-754
Bryan
Bryan Davis Wikimedia Foundation bd808@wikimedia.org [[m:User:BDavis_(WMF)]] Manager, Cloud Services Boise, ID USA irc: bd808 v:415.839.6885 x6855
MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
mediawiki-l@lists.wikimedia.org