Composer is a PHP package management system and it is needed to manage some important Mediawiki extensions. This section lists all sorts of libraries you need to have if you plan to use extensions. It is better to have them installed before installing the Mediawiki, since the installation script can detect and configure these. You then also should configure the LocalSettings.
In your Local file use something like this. You may have to adapt the executable path, e. In principle one should use the latest stable release when you install a new wiki. This way you are fairly sure that new extensions you will install should last a bit. Alternatively, install the latest long term version see next item. We then recommend upgrading to each new release until you reach an LTS long term support version.
As of Sept , use 1. IKt should last until June Read Version lifecycle release policy from Mediwiki. This is a JavaScript web server and is needed for the VisualEditor. Its installation is explained in VisualEditor , since it is is needed for that extension.
Its installation and configuration is explained in Mediawiki collection extension installation. I usually prefer to install all portals in some other place and then configure the web server to include this place using the Apache ALIAS directive see below. IMHO, this makes administration easier in the long run. Also, in times of crisis it's easier to take a portal offline: just disable the ALIAS or restrict access to the local network.
On system that shares various web applications, I suggest using a virtual web server name for your wiki. Ask for an Internet alias instead of using the "main name of your machine". This way you can migrate your wiki more easily from one machine to another. The file will now be loaded into the apach2. Mediawiki takes quite a lot of memory. Some extensions can run for quite a while. If you don't have many other portals where scripts can run wild, you could use fairly large values here even go higher than below.
Notice that php. Allow people time for editing students will freak out if the wiki refuses to save and edit, else explain that they could copy the edited text someplace and then edit again. You will have to create a database we strongly suggest not to use prefixes, i. For such simple operations we suggest using the mysql command line as shown below.
If you want to be able to upgrade quickly or work with a bleeding edge alpha version sometimes this is recommended, sometimes not , the simplest way is using GIT formerly SVN was used. The reason not to use the latest version, is that extensions can break and that very early versions may have bugs. Now make sure to select the right version, e.
Location of the repositories changes all the time, e. It will tell where to look for. Go to the long Wiki URL this depends on how where you installed the wiki and how you created your web server alias, see above.
Environmental checks should be just fine, e. Answer all the questions : I suggest using most of the defaults, in particular the ones that relate to database architecture. Since you will have to tune the configuration file manually, you will have learn how to configure the MediaWiki manually anyhow. Just make sure to remember: database name, database user, database user password. If you work in a decent environment, just edit file LocalSettings.
Else you will have to copy the file to the server. In particular, make sure that short URLs work and that you have a skin the graphical user interface. Vector skin is defined as default, but the Wiki won't find it. See also the section on skins.
Usually modifying any file in the source code because you will have to redo the fixes after each minor update. In addition, git will become confused. InkStitch is an Inkscape extension to create digital embroidery designs. But see also the composer information below. You may have to rerun it using various weird tricks to get it going Sometimes the composer is way to sensitive to differences in subversions.
Try the following even if it is not a smart thing to do per se We repeat: If you get Error: your composer. Run "composer update --no-dev" to install newer dependencies and you are sure that you installed the correct versions, try:. See ManageMediaWiki for some rather chaotic additional tips. Unless you use some configuration extension, all the configuration except for styles and user messages is done in file LocalSettings. File cache can speed up serving non-dynamic contents a lot.
However, caching is a complicated art Rights and icons I suggest creating a subdirectory of the main directory where you can put picture files for icon that are read in via PHP. I used tecfa , pick your own, e. Permissions: I suggest using somewhat restrictive permissions, i. However, this cannot last for long unless you can hire a community manager to clean up spam.
Once your wiki is online, it will take only a few month before it's filled up with tens of thousands of spam pages. We shall explain later how to manage user rights and how to fight spam.
This is just for starters Files uploads: In an educational setting you might allow more file formats than in a fully open wiki. Certainly PDF should be included, unless you have some stable and easy to use document systems that is available to your learners. Add a comment.
Active Oldest Votes. Improve this answer. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Explaining the semiconductor shortage, and how it might end. Does ES6 make JavaScript frameworks obsolete? I installed mediawiki in subdomain. Check file permissions of the LocalSettings. Since it isn't now generated on the server but you need to manually upload it, it may have the wrong permissions and isn't readable by the server.
I had this problem after transferring from one server to another. It was caused by the LocalSettings. It didn't matter on the previous server because it was windows-based, whereas the new one is Linux where case matters. This is not the problem. I have the file LocalSettings.
It is the installation of a mediawiki 1. If you see a value in this file that you wish to change, take note of it. Later, you can add the value to the LocalSettings.
Configuration should be done in the LocalSettings. It looks very similar to DefaultSettings. Type the following command to open the file for editing:. This file is written in the PHP programming language, but the syntax is relatively easy to understand. For the most part, you will see the following syntax:. This file has many different configuration settings, but not all of the available settings are defined here.
Generally, only those settings with values that contradict the defaults found in DefaultSettings. If you wish to change the settings of anything found in DefaultSettings. If it does not exist, add it to the bottom. Before making any changes, go ahead and backup the configuration file in case something does not work as expected:. You selected a name for your site during initial configuration.
The second variable sets namespace for the pages that refer to the wiki itself. It cannot contain spaces, so we use underscores instead.
0コメント