Re: [Semediawiki-user] Installation of SMW on a Wiki family

[Temlakos <tem...@gm...>]

On 09/30/2015 09:48 AM, Temlakos wrote:
> We don't define subdomains for each language. Instead we put the 
> primary (English-language) wiki in public_html (ours is a shared or at 
> best a semi-dedicated host) and each other language, and our media 
> pool, in a separate directory. I understood I could specify the 
> instance of LocalSettings.php appropriate to each maintenance script. 
> Perhaps no one in your administrative community has looked up the 
> parameter support for MediaWiki's maintenance scripts? That's what I 
> seek to learn: what parameters do the SMW scripts take?
>
> After long and careful consideration, I decided /not/ to install the 
> Semantic Bundle. I'd much rather use Composer to get the 
> latest-and-greatest version of SMW, and add other extensions as 
> needed. (The SB seems to be stuck at SMW 1.9.2, whereas SMW itself is 
> up to version 2.2.)
>
> As far as I can tell, the only problem the maintenance scripts have 
> with symlinks, is that they don't know which LocalSettings.php you're 
> pointing to. That's what the --conf parameter for MediaWiki's 
> maintenance scripts is for: to tell the script "update.php", for 
> example, /which/ database to update. But I don't know where anyone has 
> documented the parameter support for SMW's maintenance scripts.
>
> Temlakos

Postscript: once again I found the solution to the problem of how to 
tell a maintenance script which instance of MediaWiki you want it to 
work on.

The file README in the directory /maintenance of SMW gives the full 
instructions. But anyone can read them here:

https://raw.githubusercontent.com/SemanticMediaWiki/SemanticMediaWiki/master/maintenance/README

Briefly, any maintenance script takes the parameters --conf and --aconf. 
They let you specify LocalSettings.php and AdminSettings.php for your 
particular installation. It's also wise to set the environment variable 
MW_INSTALL_PATH to the absolute path to the directory holding your 
particular MW installation--where LocalSettings.php actually sits.

I also gather that rebuildData.php replaces refreshData.php and adds 
more features.

Temlakos

>
> On 09/30/2015 04:50 AM, egel wrote:
>> We have a Wiki family/farm/cluster (www.scoutwiki.org  ) and some wiki's
>> are using SMW. We use a Drupal-style sites configuration. We use two
>> copies of the MediaWiki code. One is used by the webserver and one is
>> used by the maintenance scripts. Some maintenance scripts don't like
>> symlinks, so it is best put the "hard" extensions directory in the
>> "maintenance" directory and a symlink in the "webserver" directory. In
>> the separate LocalSettings.php files is only $wgDBname defined, the rest
>> is defined in the common InitialiseSettings.php and CommonSettings.php
>> files. Almost like Wikipedia does it. Before running a maintenance
>> script a LocalSettings.php file is copied to the "maintenance"
>> directory.
>>
>> SMW and some other extensions and skins must or can be installed with
>> Composer. It is not easy to have Composer installed extensions when not
>> all your wiki's want or need all those extensions. Then you need some
>> hacks or all wiki's in separate directories.
>>
>> A manual for our upgrade procedure:
>> https://asso.scoutwiki.org/MediaWiki_upgrade
>>
>>
>>> Everyone--but especially Yaron Koren:
>>>
>>> The MediaWiki manual recommends, for setting up MediaWiki code for
>>> multiple wikis with shared resources, to install the code for one of
>>> them (usually the media pool, but not necessarily) in a particular
>>> folder, then to open a new folder for every secondary wiki, install the
>>> MW code in each one, and then--this is the key--replace most of the
>>> subdirectories with symbolic links. That includes the extensions
>>> subdirectory. (They specifically say /not/ to do this with the
>>> directories named cache, mw-config, or images, for obvious reasons.)
>>>
>>> Question: do you recommend installing SMW or especially the Semantic
>>> Bundle in one "hard" extensions directory with symlinks to several
>>> others?
>>>
>>> My new Web hosts assure me Apache is configured to follow symlinks.
>>>
>>> If I have to, I can install SMW or SB separately, in separate
>>> extensions
>>> directories, without symlinks. I want to know whether that's necessary.
>>>
>>> Temlakos
>>>
>>> http://creationwiki.org/
>