Extension:Farmer/fr

English - Français

À propos
Farmer est un outil qui vous permet d'administrer un ensemble de projets Mediawiki aussi bien qu'il modifie la configuration grâce à une interface Web.

Changelog

 * 0.0.2 : Gère l'apparence par défaut ainsi que les extensions gr«ce à l'interface Web. L'administrateur Farmer pour sélectionner les extensions disponibles pour l'ensemble des sites. Chaque wiki peut sélectionner les extensions qu'il veut activer.
 * 0.0.1 : Version initiale. Possiblité de créer un nouveau wiki grâce à une interface Web.  Peut aussi modifier les habilitations wiki par cette même interface.

Préfixe de la Table
Farmer impose que toutes les tables Mediawiki aient un préfixe, le wiki par défaut inclus. En l'absence de tel préfixe, chacune d'entre elles devra être renommée. Pour cela utiliser la requête SQL suivante :

En se basant sur la version 1.12alpha de Mediawiki, il est conseillé de déparer le préfix par _-_ afin d'éviter des problème de reconnaissance de la table. Si vous désirez ajouter le préfix admin, je conseille donc d'opérer de la façon suivante :

Répertoir accessible en écriture pour les fichiers de configuration des Wikis
Farmer écrit les configurations pour chaque wiki sur le disque. Le fichier permet l'accès au wiki grâces aux données écrite dans ces fichiers. Ceci signifie que le répertoire extensions/Farmer soit accessible en écriture. Ceci implique, notamment sous UNIX, ou LINUX, de lancer la commande chmod a+w extensions/Farmer -R.

Nettoyer LocalSettings.php
La configurration de LocalSettings.php doit être limitée au minimum. En effet, Farmet s'occuper de l'environnement globale de wiki par défaut, et ajuste les variables.

Ainsi, Farmer réduit LocalSettings.php au simple rôle de configuration globale de votre ensemble MediaWiki. Le code de ce fichier s'appliquera sur l'ensemble des wiki dépendant du site qui administrera tout l'ensemble. Vous pouvez continuer d'ajouter les extensions et les variables globales. En revanche, chaque variable propre à un sous projet ne devrait y figurer.

La liste des variables suivant ne devraient pas être définie dans votre LocalSettings.php.
 * $wgSitename
 * $wgDBprefix
 * $wgLogo
 * $wgGroupPermissions

En réalité, si quelques variables y sont définies, elles seront écrasées par Farmer. Cependant, une bonne pratique de la programmation est de ne pas définir des variables pour les sous-wikis dans ce fichier.

Choisir une stratégie d'hébergement
La stratégie d'hébergement consiste à savoir comment les wikis seront accessibles par une URL. En voici quelques exemples.

Wildcard DNS
La passerelle DNV se réfère par l'usage d'un hôte virtuel et d'une entrée DNS pour établir tous les sous-domaines d'un hôte vers un wiki unique.

Par exeple si votre wiki se trouve à  http://farm.mondomaine , les wikis seraient disponible sur  http:// wiki1.farm.mondomaine,  http:// wiki2.farm.mondomaine, etc.

Le préfixe de l'URL
Le préfixe de l'URL se réfère à l'identification d'un wiki par une composante du lien. Si vous avez un site  http:// farm.mondomaine, les wikis seraient accessible par  http:// farm.mondomaine/wiki1/,  http:// farm.mondomaine/wiki2/

Si vous n'avez pas la possibilité de créer une entrée DNS, vous serez donc obligé d'utiliser cette méthode.

Autres possibilités
Parce que Farmer vous permet de définir votre propre fonction pour planifier une requête vers un wiki, il est possible de créer une telle planification qui ferait ce que vous voudriez. Ainsi, vous pourriez planifier différents niveaux de domaines pour les wikis qui seraient tous créés par une seule installation de Mediawiki. Vous pouvez même planifier vers un wiki différent sur votre navigateur, etc. Tout dépend de vous.

Patches
Farmer exisge que soient appliqués quelques patches pour qu'il fonctionne convenablement. Ils concernes quelques fichiers du répertoire includes/ de mediawiki.

Compte tenu des récentes modifications de mediawiki depuis la création de l'extensions, les patches ont été modifiés depuis.

Tables partagées
À l'origine, le rapport #2396 contenait un patch pour les tables partagées pour l'ensembles des wiki. Ce patche avait été publié sur my patch lequel est devenu obsolète.

Il est donc conseillé d'utiliser le patch suivant :

Une fois votre patch installé, indiquer les paramètres suivants dans LocalSettings.php :

Il serait encore mieux d'y écrire directement le nom complet de la table partagée. Plusieurs problèmes ont été relevés avec cette configuration. Si vous avez le préfix admin, à titre d'exemple, j'écrirai directement :

Ceci partagera les tables 'user', 'user_groups', 'interwiki', and 'math' sur l'ensemble des wikis de Farmer.

Il est possible que Farmer puisse supporter, un jour, des bases de données non partagées `user` et `user_group`. Il semble qu'il serait plus logique pour eux qu'ils demeurent partagés car ce serait désavantageux d'administrer plusieurs comptes sur le même site.

mysql_errno fix
Si vous tournez avec MediaWiki trunk, passez à l'étape suivante. En revanche, pour les versions 1.7.1 et précédentes, vous devrez modifier dans Database.php, les fonctions fetchObject, fetchRow, et numRows qui appellent mysql_errno directement.

Vous devez changer ceci pour la lecture :

Obtenir le code source
Le code source est disponible sur le site officiel Subversion sous extensions/Farmer

Copier les sources vers le répertoirs extensions/
Copiez le code source ainsi téléchargé vers extensions/Farmer.

Installation dans LocalSettings.php
À la fin du fichier LocalSettings.php, ajoutez :

<!--

Configure Farmer
Farmer must be configured before it will work. Until it is configured, your wiki will be broken.

Farmer's behavior is affected by the settings in the global $wgFarmerSettings variable, which is created when Farmer.php is included.

To set a setting, alter the values in $wgFarmerSettings between the require_once('farmer/Farmer.php') and $wgFarmer = new MediaWikiFarmer($wgFarmerSettings); lines in LocalSettings.php.

You will have something like the following:

$wgFarmerSettings variables and definitions
The follow are the possible configuration parameters that affect Farmer's behavior.


 * defaultWiki : The name of the default wiki. This corresponds to the table prefix of the default wiki.  The default wiki is also the main wiki on your site.  It is the only wiki whose Special:Farmer page can be used to create wikis.  This master wiki also contains messages in the Mediawiki namespace which are used to affect new farms.  When a wiki cannot be identified by wikiIdentifierFunction (see below), the accessed wiki will be the value of this variable. This value must also be in lower case. This variable must be set.


 * configDirectory : Directory where Farmer will place and read per-wiki configuration files. This directory must be writable by the web server.  It defaults to the /configs/ directory under the directory where Farmer.php resides.  For security considerations, this directory should not be accessible via the web.  It is a good idea for this directory to reside outside of your document root.


 * wikiIdentifierFunction : When Farmer runs, it calls a function that attempts to figure out the accessed wiki from environment variables. This parameter defines which function is called to do this.  The value of this configuration option is actually the first parameter to PHP's call_user_func.  The MediaWikiFarmer class has a few built-in methods which you can use:  _matchByServerName, _matchByURLRegExp.  If you require more sophisticated behavior than the provided function for determining the name of a wiki that was accessed, you can write your own function to do the mapping and set this parameter to be the name of that function.  The default value is array('MediaWikiFarmer', '_matchByURLHostname')


 * matchServerNameSuffix : When using _matchByServerName as the wikiIdentifierFunction, this parameter sets the suffix of any hostname that represents a wiki. For example, if you are using wildcard DNS to identify individual wikis (wiki1.mydomain.com, wiki2.mydomain.com, etc), then the suffix will be mydomain.com.  In other words, _matchByServerName will return every character up until the period before matchServerNameSuffix


 * onUnknownWiki : Function to call when an unknown wiki has been accessed. The value of this configuration option is the first parameter to PHP's call_user_func.  The function identified by this variable is called when the wikiIdentifierFunction has identified a wiki from the environment, but Farmer is unable to verify that this wiki exists.  The default value is array('MediaWikiFarmer', '_redirectTo').  When this function is called, the first parameter will be the name of the wiki, as identified by wikiIdentifierFunction.


 * redirectToURL : When onUnknownWiki is set to array('MediaWikiFarmer', '_redirectTo'), this option sets the URL that will be sent in a Location HTTP header. $1 in this URL will be replaced with the wiki name, as passed to the function set by onUnknownWiki.  It is a good idea for this URL to point to the Special:Farmer page on your main wiki or to instructions on how to create a wiki in case normal users don't have permission to create wikis.


 * dbAdminUser : Database user that has access to create tables on $wgDBname


 * dbAdminPassword : Password for dbAdminUser


 * newDbSourceFile : SQL source file that will be used to create a new wiki's database tables. The file must be formatted like the tables.sql files in /maintenance/ (table names must be prefixed with /*$wgDBprefix*/.  This variable defaults to daughterwiki.sql, which is is distributed with Farmer.  This SQL file is /maintenance/mysql5/tables.sql without the user, user_groups, math, and interwiki tables.  If you have installed custom extensions that require their own tables, you will want to create a new .sql import file and change this setting to link to it.


 * dbTablePrefix : Prefix for all tables in your database. This is normally not needed.  This would be needed if you only have permission to create tables with a specific prefix, etc.


 * dbTablePrefixSeparator : String to place between the wiki name and the MediaWiki table name. This is used to make table names easier to read, process, etc.  If not set to anything, a table name will just be the wiki's identifier plus table name.


 * defaultMessagesFunction : Function to call that returns an array of the messages to put in the Mediawiki namespace of newly created wikis. The value of this parameter is the first argument to PHP's call_user_func.  The returned array should have the message name as the key and the message as the key value.  If not defined, will use $wgAllMessagesEn to populate the message namespace.
 * perWikiStorageRoot : Parent directory where per-wiki documents (images, uploads, etc) will be stored. This directory everytually finds its way into the $wgUploadDirectory variable.  This directory needs to be writable by your web server.


 * defaultSkin : The skin to use for newly-created wikis. Takes same values as $wgDefaultSkin.  Defaults to monobook.

Running Farmer the First Time
After Farmer is installed in LocalSettings.php, Farmer should be usable. The first request to hit your wiki after Farmer is installed will do some special things. When your default wiki is accessed, Farmer will automatically create its configuration file and other files necessary for Farmer to work. If the directory defined in configDirectory isn't writable, Farmer will throw an exception and your wiki will not be usable. If you don't get any error messages and you can access your wiki, then everything appears to be configured properly!

Customizing Farmer Messages
Before you do anything with Farmer, you will need to customize some default system messages. Go to Special:Allmessages on your wiki. All of Farmer's messages are prefixed with farmer to keep them organized. As is the case with all extensions, it is important that you protect the pages corresponding to all of Farmer's messages to prevent any user from editing them. This is especially important with Farmer, as some of the system messages have a critical impact on Farmer's operations.

Two system messages that you will want to configure will be farmerinterwikiurl and farmerwikiurl.

farmerwikiurl
farmerwikiurl is the template for the URL of a wiki in your farm. $1 represents the wiki name. Customize the URL to match your wiki hosting strategy.

farmerinterwikiurl
farmerinterwikirul is the template for the URL used for interwiki links. $1 represents the wiki name. $2 represents the article title. Chances are this variable looks very similar to farmerwikiurl.

Setting Options for Default Wiki
Since the default wiki's configuration file is generated automatically when Farmer loads the first time, its settings are incomplete. You will need to visit Special::Farmer on your site to set them! Bad things happen unless you do this. In order to set the appropriate settings, you will need to be logged on as someone with the farmeradmin privilege. This privilege is automatically given to members of the sysop group. If you have this privilege, on Special:Farmer of your wiki, you should see a link to Administer this Wiki. Follow it.

Setting Title
On Special:Farmer/admin, it is imperative you set your wiki's title. The title can only be set once, so make sure it is correct! The title is actually an alias for $wgSitename. Therefore, it is also the name of the project namespace.

Description
Description is a text description of your wiki. You can change it at any time. It is used in the wiki farm directory.

Permissions
Set the permissions for your default wiki. All permissions default to closed. You will probably want to open up your wiki so people can actually edit it.

Using Farmer
One interfaces with Farmer via Special:Farmer. From there, one can perform many tasks.



Creating Wikis
Wikis can be created by following a link on Special:Farmer. This link is only available if the following conditions are met


 * 1) You are currently on the default wiki
 * 2) The current user has the createwiki privilege (by default assigned to the sysop group)

When you click on the link, you will see a web form with three elements.


 * Wiki Name : The name of your wiki. This will be used as part of the URL.  The name is reduced to lowercase and all non-alphanumeric characters are removed.
 * Wiki Title : The title of your wiki. This is effectively $wgSitename.  Spaces are removed for interwiki prefix compatibility.
 * Description : Description of your wiki to appear in wiki farm directory

Once you have filled out these form elements, press the button to verify them. The next page will show you what the values were modified to (if necessary). It will also give you some basic information about how your wiki will work (what the URL is, project links, etc).

To confirm that these settings are correct, press the Confirm button.

When you press the button, the following happens:


 * 1) Your wiki's basic config file is generated with the information you supplied
 * 2) The SQL in the file specified by Farmer's newDbSourceFile configuration setting is executed, creating the necessary tables
 * 3) The wiki's main page is set to the content defined in the farmernewwikimainpage system message
 * 4) The new wiki's system messages are populated
 * 5) The interwiki table is updated with a reference to this wiki
 * 6) The person who created this wiki is added to a group of the name  [farmer][wikiname][admin] , where wikiname is the name of the wiki.

If everything works, you should see a message saying your wiki was created. This message will contain a link to your new wiki.

Managing Wikis
Farmer allows system operators as well as per-wiki admins to have control over some aspects of individual wikis. These controls can be found at Special:Farmer/admin. Currently, these controls just allow you to set the wiki description and define permissions for your wiki. In the future, it is hoped to provide a much more verbose interface to other variables.

Manage Extensions
Farmer allows farmer administrators to define extensions which can be selected for loading by member wikis.

Defining Loadable Extensions
Users with the farmeradmin privilege may access Special:Farmer/manageExtensions to define extensions which can be used by wikis in the farm.

On this page, you will see a list of extensions which are already loaded, a list of PHP's include peth, and a form to define a new extension.

Unfortunately, MediaWiki does not have a good interface to abstract loading extensions. So, we have to give Farmer the filenames of extensions we wish to load. If the filename is incorrect, don't worry. Farmer verifies that the file exists and is includable before adding an extenion to its list. If there was a problem adding an extension, Farmer will say so.

Per-Wiki Extension Management
Child wiki administrators may go to Special:Farmer/admin to select which loadable extensions to activate on a particular wiki. -->

Voir aussi

 * Extension:Read Restrict
 * Manual:Wiki family