Wiki configuration

From eg

Any wiki configuration depends strongly on web configuration as wiki software is invariably an HTTP-based service.

On this page, cover only the configuration questions specific to this use of apache. Only the lowest level wiki policy issues should be covered.

This page contains information about mediawiki -based wiki configuration. It explains wiki software in the context of open configuration projects and large public wikis in particular. For details of the wiki configuration of eg:itself see eg:wiki configuration. For information about policy matters relating to wiki use see wiki policy. For the actual eg:policy on wiki use see eg:wiki.

See mediawiki gronks for some difficult-to-overcome issues and wiki workarounds.

[edit] eliminating /index.php/

The rewrite rules required to eliminate the /index.php/ cruft from rigid designators are documented along with some non-rewrite approaches. This has not been done yet, but will be.

[edit] subdomain

The subdomain "wiki." is commonly used in large public wikis such as wiki.creativecommons.org. Unfortunately it tends to imply that this is the only wiki in use at that domain which isn't ideal. Using the name of the service is a more common practice, e.g. develop.consumerium.org for the develop wiki of consumerium.org which intends also to create "research" and "publish" wikis to create a pipeline from least to most controlled. This might be useful for a pipeline of sysop publications or even just a credible local tech manual.

It's been proposed by trolls to use "eg." as in eg.zooid.org for this wiki. This might be used by other wikis following the same conventions, e.g. eg.shields.org, without implying it's the only wiki.

Also obviously any other subdomain could be used to mirror that of the service intended, e.g. a simpol wiki could have sp.zooid.org, etc..

[edit] when to settle the above

The above can be detailed on all issues after scope issues are settled.