Question

We're using TWiki as a knowledge base in our intranet. As we're still in an early phase, there are frequent changes to the TWiki system (new plugins, changes to skins etc.). I'm now looking for a way of setting up a parallel test system where I can try out all changes before rolling them out to the live system.

I can see two extreme solutions:

• Setting up a virtual test system (e.g. VMWare) to keep the two systems completely separate. A disadvantage of this method is that the systems don't share the content.
• Running a second TWiki on the same server as the live system in the same Apache instance (how would I do that?). Disadvantage: changes to the base system (i.e. Perl upgrade) would influence both systems.

I would appreciate it if you could share your experiences on running a test system.

Environment

-- MartinKaufmann - 16 Jul 2007

Answer

If you answer a question - or have a question you asked answered by someone - please remember to edit the page and set the status to answered. The status is in a drop-down list below the edit box.

I use both approaches :), to test TWiki plugins and changes, I use a second TWiki, often installed in a user's public_html dir, whereas if I'm testing perl, system or other changes, I'll use a VMWare host so i can do lots of rollbacks.

-- SvenDowideit - 03 Aug 2007

-- SvenDowideit - 18 Aug 2007