User talk:Legoktm/Packages

Jump to navigation Jump to search


Fantastic work! Let's make sure we get the word out to the world. Added to for now. Nemo 17:30, 22 September 2016 (UTC)[reply]

Thanks :) It was on my list to update that page - I've removed all the old information from there and made it a stripped down version of this one. Legoktm (talk) 20:02, 22 September 2016 (UTC)[reply]
Ok, that works too. If the old package is not even worth mentioning, should you perhaps ask to take over the "official" Debian package? Nemo 20:06, 22 September 2016 (UTC)[reply]
Er, I already *do* maintain the official package [1]. Debian Jessie users are installing the package from the official Debian repositories, and it's going to be included with the Stretch release. Legoktm (talk) 21:07, 22 September 2016 (UTC)[reply]
Oh good. From the page I got the impression that the PPA was the only option available to download the package. Nemo 21:22, 22 September 2016 (UTC)[reply]


Hi there, I see a comment that extensions are no longer supported. But how can I get them back into working order? I am looking for the math and graphviz extensions. How should I install them / clean up the old files in

/etc/mediawiki-extensions/* ?

Thank you!Florihupf (talk) 23:24, 10 October 2016 (UTC)[reply]

Hi Florihupf, you should install extensions into the normal MediaWiki extension directory, and add the proper wfLoadExtension(...) calls to your LocalSettings.php file. Legoktm (talk) 05:07, 4 November 2016 (UTC)[reply]
Ok, it is all good now! Thanks! Florihupf (talk) 19:02, 16 December 2016 (UTC)[reply]
Sure that placing in /var/lib/mediawiki/extensions is the proper way to do it with this package? I mean, why so /etc/mediawiki-extensions/extensions-available and /etc/mediawiki-extensions/extensions-enabled? --Valerio Bozzolan (talk) 18:24, 4 July 2017 (UTC)[reply]
Yes. Those are legacy and left over from the old mediawiki-extensions packages. Since people may have referenced them in their LocalSettings.php I didn't remove them yet. Legoktm (talk) 23:53, 11 July 2017 (UTC)[reply]

I have now documented this in Filesystem section of the page. Legoktm (talk) 04:10, 17 August 2017 (UTC)[reply]

Beyond Debian[edit]

At FOSDEM the people behind stressed that they have a lot of computing resources available for people to make packages for other distributions as well. Is it worth trying to get more packages? --Nemo 20:06, 7 February 2017 (UTC)[reply]

That would be nice if someone else wants to step up, but I don't have time to extend this past Debian right now. The main part that takes up my time isn't the packaging itself, but ensuring everything is properly licensed, making sure new stuff isn't introduced that is problematic for Debian (e.g. [2]), and then keeping up to date with Debian policy changes. Legoktm (talk) 04:17, 17 August 2017 (UTC)[reply]

Potential double negative?[edit]

> In the past these packages were severely outdated ...

Maybe this whole subclause should be moved to its own notice box: "This package supercedes all previous packages, which are now dangerously outdated ...". Awesome work packaging, thanks! I'm happy to be trying out on puppetized VPS for a personal project. Adamw (talk) 07:52, 11 July 2017 (UTC)[reply]

Presentation at DebConf in Montreal 2017[edit]

Hello, I will be presenting about my experiences packaging MediaWiki and working with the Debian community. If you're interested, come check it out :) Legoktm (talk) 18:53, 24 July 2017 (UTC)[reply]

Video and Slides are available on Commons now :) Legoktm (talk) 04:18, 17 August 2017 (UTC)[reply]

Other apache aliases?[edit]

Is it okay to edit /etc/mediawiki/mediawiki.conf? I'm assuming not. I'm attempting to write some docs about how to install multiple wikis (on a VPS) in the simplest way possible. At the moment, I'm thinking it's best to create a /etc/apache/sites-available/mediawiki.conf and add everything there. Sound appropriate? Sam Wilson 01:51, 29 July 2017 (UTC)[reply]

Yes, it's probably OK to edit that file. It's actually not used by anything (it exists just in case someone still uses it from an older package version), the real config file is actually in /etc/apache2/conf-available/mediawiki.conf. On a wiki farm I have running using the package, I have one apache conf file, and then have LocalSettings.php check $_SERVER['SERVER_NAME'] to figure out the dbname, and go one from there. Legoktm (talk) 16:38, 7 August 2017 (UTC)[reply]


I'm suggesting to add a note that, after installation, for Ubuntu Users, you'd have to follow Manual:Running_MediaWiki_on_Debian_or_Ubuntu#Configuration_mysql to configure MySql before setting up the WIki for the first time. Masssly (talk) 08:49, 14 October 2018 (UTC)[reply]

Short URLs[edit]

Would /etc/apache2/sites-available/default-ssl.conf be the correct file to modify to add rewrite rules for Short URLs? -- Bryandamon (talk) 05:54, 15 October 2018 (UTC)[reply]

It sounds like /etc/apache2/conf-available/mediawiki.conf is the preferred location although the above location would work as well. -- Bryandamon (talk) 06:32, 24 October 2018 (UTC)[reply]

VisualEditor in 1.35... does it work?[edit]


I've upgraded a Debian GNU/Linux buster MediaWiki to buster-backports and everything was OK. I knew that VisualEditor was provided out-of-the-box in this version but actually it's not. Does it work in your installations? If yes, can someone share your related configuration? --Valerio Bozzolan (talk) 12:08, 3 December 2020 (UTC)[reply]

You need to add wfLoadExtension( 'VisualEditor' ); to your LocalSettings.php, and then it should work (note that it doesn't work on SQLite yet). What errors/issues are you getting? Legoktm (talk) 21:50, 3 December 2020 (UTC)[reply]
Uhm. I've a missing VisualEditor/extension.json and it's also trying to open a file that I do not found nowhere (webrequest.php). You can see this paste and this one. --Valerio Bozzolan (talk) 10:23, 4 December 2020 (UTC)[reply]
@Valerio Bozzolan: Why is it trying to load extensions out of the /home/www-data/ directory? Extensions are supposed to be in /var/lib/mediawiki/extensions. Did you change $wgExtensionDirectory? And the WebRequest error is a red herring, see phab:T261260. Legoktm (talk) 22:14, 8 December 2020 (UTC)[reply]
Yes Done Uhm. It seems with your question you given me enough inputs to fix my issue. You remembered me that I adopted your package because it allowed me a workflow I love so much: I'm keeping everything on my legacy filesystem position, symlinking core stuff to /usr/share/mediawiki and shared extensions to /var/lib/mediawiki. In this way the wiki owners are independent by the sysadmin and can change some stuff via FTP, and decide to adopt shared simlinked extensions or just drop the symlink and upload a custom version or additional extensions. This is a lazy but powerful solution but... we forgot to symlink the new VisualEditor extension. For some reasons we were sure only the extension.json file was missing but the whole directory was missing :) Thanks really. --Valerio Bozzolan (talk) 23:52, 8 December 2020 (UTC)[reply]
Aha! Glad you were able to get it working. Legoktm (talk) 09:29, 10 December 2020 (UTC)[reply]

Interest in having skins and extensions packaged?[edit]

Mostly as a proof of concept, I've packaged Skin:GreyStuff and Extension:YouTube. These are available as mediawiki-skin-greystuff and mediawiki-extension-youtube respectively (just in buster-backports for now, Ubuntu PPA to come). Installing the package just drops the files in the right spot, you still need to manually wfLoadExtension/Skin them.

Are people interested in seeing more extensions/skins packaged? If so, which ones? Legoktm (talk) 01:09, 15 December 2020 (UTC)[reply]

Running inside Docker[edit]

I am looking to run semantic mediawiki inside docker. The existing docker implementations I am finding out of date, so I am thinking a docker file that builds from here is what will work for me. I post this here in case it is helpful.

Docker file

FROM Debian:latest


RUN apt-get -y update

RUN apt-get -y upgrade

RUN apt-get install vim zip unzip net-tools --yes

# prevent mediawiki install asking for input

ARG DEBIAN_FRONTEND=noninteractive

RUN apt-get install mediawiki --yes

# install composer in the user mediawiki directory

RUN php -r "copy('', '/usr/share/mediawiki/composer.phar');"

RUN php /usr/share/mediawiki/composer.phar

RUN apt-get clean

# run apache




@RibeyeOnTheBone: as I mentioned on IRC, you should use composer v1. Also I would recommend building on top of Debian, not Ubuntu. If you want to use Ubuntu I recommend using my PPA Legoktm (talk) 23:50, 29 June 2021 (UTC)[reply]