Requirements

There are several requirements to be met:

• Although extensive MOO programming skill is not required to install Aloha (my case is the best example), a minimum is still required. For instance, one should be familiar with modifying properties of objects, and with the use of the eval() function (usually noted in this document as a semi column: ;$kahuna.property=1).
• there are lots of room for improvement of current packages and especially for new modules that can add more functionalities. The best example is at LogMOO where Aldon et Al. made numerous fixes and new features. In this case, a stronger MOO programming background is required.
• A MOO server and database (I was not sure I needed to put that one in, but since I'm at it...)
• HTML!! I know... I don't like HTML either, but it will be assumed that you know how to write your own. What is by meant by knowing HTML is not knowing how to use an HTML editor; you will have to know what the basic HTML tags mean to understand what is being done during data transfer and in order to create your own utilities.
• The possibility to use one more port on the actual server. Indeed, the MOO server is usually accepting connections through the default port 7777 (which can be modified in options.h or $network.port). Aloha will need another port through which packets coming from browsers, can be accepted to the MOO. Hence, Aloha will listen to a DIFFERENT port. That is, ;listeners() will display another object (Aloha) and the port that is being used. It is therefore, imperative that the server on which the MOO system is running does not block that extra port (through firewall rules such as iptables or ipchains).
• It will be assumed through this document that a *nix box is used. Although, there is nothing (except for some FUP functionality) that prevents other OS to handle it. Be aware though that no support will be given for problems that arise from other OS than *nix (I know I just said there should not... but I was thinking about modules that use FUP). Some syntaxes in this document will therefore refer to *nix commands: simply find the corresponding for your own OS.
• For the bar bone system of Aloha there is no need for other Web server. However, Aloha only support TEXT based display. The GUI WILL need another web server to handle all the pictures and non TEXT based data. Apache is the one that has been used for this development; however, any should be able to fit the job task. I'd like to point out that you are on your own concerning the httpd.conf or any other configuration concerning the web server that you will use for pictures serving.
• If you already have a MOO web server installed, or you are using a database which came with a MOO web server and is running, there is nothing that prevents you from installing and running Aloha as well at the same time. You actually could use several version of Aloha at the same time if you need to. The only requirement is that each listen to its OWN port (otherwise, you will get in trouble).
• If you already have an old version of Aloha prior to 2.1 you can still install the newest without any conflict. This is one of the reasons it has been renamed $kahuna and that only this guy has been @corified. You therefore can have several version running at the same time.