Does anyone have experience using version control software to manage MediaWiki-based wikis?

We use MediaWiki for user documentation. As the sole author, I can create and manage new versions of the wiki to support version versions of software.

I am looking for recommendations for managing the switch on a new instance of MW (to coordinate with the new software version). Here's how I do it now:

The MW instance in the / wiki supports production software (v1). In a separate instance of MW, I create / v 2. When it came time for the release of the new version of the software, I simply backed up v1 (MySQL database and HTML files), then copied v2 (MySQL database and HTML files) to the / wiki folder.

Is it practical? Could this be better / safer / more efficient? Thanks a lot, Evelyn

+4
source share
1 answer

Another approach might be to use wiki software, such as ikiwiki , which has the ability to use the real version control software on the back panel to save the wiki pages (I use it with Git). In this case, you can build v2 in another branch on another server, and then, when the time is right, switch the main server from branch v1 to branch v2.

+3
source