On 01/16/2015 05:52 PM, Legoktm wrote:
I tried getting update.php to run checkComposerLockUpToDate.php but it
was messy and didn't really work well, so I uploaded a patch[1] that
adjusts the intro text to recommend that you run
checkComposerLockUpToDate.php before running update.php.
[1]
On 01/13/2015 09:08 AM, Bryan Davis wrote:
On Tue, Jan 13, 2015 at 7:40 AM, Tyler Romeo tylerro...@gmail.com wrote:
I know we just added some new maintenance scripts for checking things with
composer. I’m sure it wouldn’t be that bad having update.php check first and
tell the user to run
The installer can be run on an existing install and
updates will be run.
-Chad
On Tue Jan 13 2015 at 10:30:00 AM Ryan Kaldari rkald...@wikimedia.org
wrote:
This may be a dumb question, but has anyone worked on creating a web
interface for running update and maintenance scripts (and viewing
Isn't web interface for maintenance imposes security risk? Also web scripts
usually are time-limited while shell scripts are not. To update text status
of web scripts one has to run batches via json, which is cumbersome.
Laravel artisan (shell script) runs composer itself, why
This may be a dumb question, but has anyone worked on creating a web
interface for running update and maintenance scripts (and viewing
associated logs)? That would probably make the whole process less painful
and confusing for 3rd party users, especially if the interface offered some
guidance on
On Tue, Jan 13, 2015 at 7:40 AM, Tyler Romeo tylerro...@gmail.com wrote:
I know we just added some new maintenance scripts for checking things with
composer. I’m sure it wouldn’t be that bad having update.php check first and
tell the user to run “composer install” before doing update.php.
The relevant link: https://www.mediawiki.org/wiki/Manual:$wgUpgradeKey
--
Tyler Romeo
0x405D34A7C86B42DF
On January 13, 2015 at 13:36:10, Chad (innocentkil...@gmail.com) wrote:
The installer can be run on an existing install and
updates will be run.
-Chad
On Tue Jan 13 2015 at 10:30:00 AM
I know we just added some new maintenance scripts for checking things with
composer. I’m sure it wouldn’t be that bad having update.php check first and
tell the user to run “composer install” before doing update.php.
--
Tyler Romeo
0x405D34A7C86B42DF
On January 13, 2015 at 08:07:34, Marcin
I am kind of late to the party but I have upgraded one of
my throaway development wikis with the usual
git remote update git merge php maintenance/update.php process
and after the above succeeded I was nevertheless greeted by:
Fatal error: Class 'Cdb\Reader' not found
exception coming out
