GenieGate is structured using a central directory for it's library files, separate directories for each deployment and web files located where it is convenient for the web master to place them.
~/geniegate/
Each instance has it's own ~/geniegate directory. This directory contains configuration files, templates and data required for it's own particular setup.
![]() | In your geniegate.ini configuration file, this is referred to as WORKDIR. |
It is recommended that you place this directory in your HOME directory, ($HOME/geniegate/ for UNIX users)
The various common.php files that reside under web/ assume ~/geniegate/ is in your UNIX home directory If this is not the case, you will have to edit common.php and specify the GENIEGATE_CONF_FILE as well as GENIEGATE_HOME.
lib/
The lib/ directory contains the global files that are used by default. Files in this directory should never be edited, instead they should be copied to the appropriate subdirectory in ~/geniegate and edited there. (very much like personalized settings in your $HOME directory for other applications such as emacs)
web/
![]() | It is extremely important that your private ~/geniegate is not accessible by the web server |
This directory will contain passwords and other information that should not be made public. It is recommended that this be in your UNIX HOME directory.
The web/ directory refers to any files that are web accessible, typically some place in your DocumentRoot.
Before we proceed to the "Quick Start" section, it is assumed that your web directory is some place in web space, and can be reached through a web browser, that your ~geniegate/ has been copied some place outside web space.