Last modified: 2008-02-04 16:52:17 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 12911 - Wiki backend, non-wiki front-end
Wiki backend, non-wiki front-end
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2008-02-04 16:50 UTC by Jonathan Kovaciny
Modified: 2008-02-04 16:52 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Jonathan Kovaciny 2008-02-04 16:50:34 UTC
I would like to use MediaWiki as the back-end content management system for a corporate site, and have a simple page-renderer of some sort which would handle the front-end. Basically this would be a stripped-down fork of MW which would not have editing or user account features but would simply serve the content. I know I can do this by configuring a standard copy of MW to disallow editing and such, but I think that a stand-alone product would be much faster and more secure and efficient.

In the setup I envision, would serve the content, and would serve the standard MW interface. The "edit" subdomain would only be visible to people inside my corporate network.
Comment 1 Roan Kattouw 2008-02-04 16:52:17 UTC
You can do pretty much all of this (except editing) by writing a front-end that uses the API as a back-end. See also [[mw:API]]

Note You need to log in before you can comment on or make changes to this bug.