Talk:FAQ

From rPath Wiki

If you have a new question for the FAQ pages, type the question below, log in or create an account, and click the edit tab above to begin editing this page.

Frequently Asked Questions:

Q: How is it possible to edit MediaWiki configuration files such as LocalSettings.php within the virtual PC interface? Is it true that if you cannot edit these configuration files then you cannot change important Wiki characteristics such as the LOGO that is being used? Any help with this matter would be MUCH appreciated.

A: Though MediaWiki software is not from rPath, I think I can answer some of this question. First, MediaWiki software itself has documentation at mediawiki.org for how to make modifications. You will notice that MediaWiki does require modifying files such as LocalSettings.php to customize its interface. When deploying MediaWiki on a personal webserver, users who are comfortable working at a command line will likely install and configure the software manually. On virtual machines, this means using console access to the system as provided by the virtual technology on which it runs. A summary of this process is as follows:

1. Install MediaWiki on an existing general-purpose operating system
2. Manually configure the software as desired at a command line
3. Manually update and maintain the software at a command line

In contrast, the MediaWiki appliance, often used as an example to show appliance building with rPath products (such as rBuilder), takes the appliance approach: provide a complete custom-configured software/virtual appliance that is ready to use as soon as it is deployed. When modifications or updates are needed, they are made by the appliance developer (using rBuilder) who makes sure all the customizations work together as desired before releasing an update. Deployed appliances then obtain the released update by using a simple one-click update mechanism. A summary of this process is as follows:

1. Create a MediaWiki appliance that includes all the desired customizations and just enough operating system to run the software (making use of rBuilder and rMake)
2. Deploy and set up the appliance on a server or in a virtual environment
3. Maintain the appliance project in rBuilder to incorporate software updates and new customizations
4. Use a one-click update mechanism on the appliance (such as that in the rPath Appliance Platform Agent) to update the deployed appliance, obtaining those updates from the appliance project maintained in rBuilder

This is a very basic overview of how installing and maintaining software is different from creating and maintaining an appliance. rPath recommends using Application to Appliance: A Hands-on Guide as an introduction to creating and maintaining your own virtual appliances.

--Stef 11:14, 7 December 2007 (EST)