Here is described how the NetLoony commands and functions turn into Apache directives. We refer to examples in configuration file text format because most experienced Apache users like to known exactly what is being written.

Section Directives

Using Apache section directives is very simple. The 'Section Structure' display instantly shows what is available and where it is. To start configuring one of these sections is simply a case of clicking on the required section, then clicking the Configure button.

The display will change, showing you further section information. If you have not fully extended the selected tree branch, this display will show you what other sections 'may' be effected.

At this point it is worth stressing:

• You must select a section before a command button, or nothing will happen.
  
  
• All section directive actions will take effect immediately within the Apache configuration file!
  
  

Adding a Section

Clicking the Add button will produce an input window, asking for the section directive type to add, and its value;

Here we are adding a <LocationMatch> section with the value 'new value' to <VirtualHost vserve1>, resulting in the following being entered into the Apache configuration file:

.... .... <VirtualHost vserve1> <LocationMatch new value> </LocationMatch> </VirtualHost> .... ....

The list of types available depends on what you are adding the section into. Therefore, we could not add a section to a <Limit> or <LimitExcept>, but we could only add a <Limit> or <LimitExcept> to, say, a <Directory>. If you are an experienced user, this sounds obvious. To a novice, it may sound confusing, but won't take long to understand. These restrictions are enforced to increase the integrity of the Apache configuration.

Deleting a Section

Clicking the Delete button will produce a conformation window, asking you to confirm the delete action. You can change your mind here, if not, the section, and all the commands within it are immediately removed from the configuration file. Note: you can not delete a the section you are currently editing.

Renaming a Section

Clicking the Rename button will produce a window asking you to enter the new value. You can cancel if you change your mind, or enter a new value; which will take effect immediately. Note: you can not rename a the section you are currently editing.

Status

Clicking the Status button will produce a confirmation window asking you to confirm the status change (enabled or disabled) according to its current state. Again, you can cancel or continue with the immediate change. Note: you can not change the status of a the section you are currently editing.

Status change example:

These are the directive settings as shown in the configuration file for:

.... .... <Directory dir1> #ExpiresActive on ServerSignature EMail UseCanonicalName off ImapMenu none #ImapDefault referer ImapBase map <Limit PUT GET> order mutual-failure </Limit> Anonymous_Authoritative Off Anonymous_LogEmail On Anonymous_MustGiveEmail On #Anonymous_NoUserID Off #Anonymous_VerifyEmail Off </Directory> .... ....

• The following message will appear after clicking the Status button:

• Clicking the Yes button will disable (comment) this section:

.... .... #<Directory dir1> ##ExpiresActive on #ServerSignature EMail #UseCanonicalName off #ImapMenu none ##ImapDefault referer #ImapBase map #<Limit PUT GET> #order mutual-failure #</Limit> #Anonymous_Authoritative Off #Anonymous_LogEmail On #Anonymous_MustGiveEmail On ##Anonymous_NoUserID Off ##Anonymous_VerifyEmail Off #</Directory> .... ....

A comment (#) means the directive will not be executed by the Apache server. The above resource, and all directives, are now completely disabled.

You will notice that some directives are double commented (##), this is so when the server is re-enabled, previously (individually) disabled directives will remain disabled.

Command Directives

NetLoony enforces most configuration rules; whole module directive sets or individual directives will become unavailable, or available, depending on what you are editing at the time. Also, duplications are avoided and incomplete commands removed.

Using Apache directives via NetLoony is very simple. The Basic Features section showed that directives are split into categories which refer to the relevant Apache modules.

Categories are often split up into sub-categories which are the related modules. The screenshot below shows directives for the core module (mod_core) which relate to access methods and behaviour. The main category is access and the sub-category is core. Here we see from the top tab that we are configuring <Directory "/usr/apache/htdocs">.

If you look carefully, you will see some other tab options (Main, require, Allow) at the bottom of the display, oposite tools. These are micro-categories within the core sub-category. It sounds like it is getting confusing, but it is very simple. The micro-categories are there because there is not enough room on the display to show all the available directives. So remember to look at these as well.

When configuring in a sub-category, no other category is effected other than the one shown. In the above screenshot, pressing the button will save all the directive settings for the core module (including Main, require, Allow micro-categories which relate to access.

	What if I think I have made a mistake while entering data?
	If you think you have made a mistake, and you have not yet pressed button, you can click the button to restore the original settings. Again, the program will restore only those settings displayed for the particular module/directives you've been editing.

	Will saving possibly overwrite any of my comments within the configuration file?
	No. To draw a parellel with HTML editors. There are some that read a page, skip anything it doesn't understand, then overwrite the original page, removing the settings it had skipped. NetLoony doesn't do this at all (you'll be pleased to hear). It simply replaces the directives you have asked to save, everything else is left alone.

	I'm not too sure what modules I have, so how do I know which module directives I can use?
	If you click on the tab, you will see the list of modules compiled into your Apache server. Also, it is always worth running a syntax check, which can be found from the category. A future update for NetLoony is to automatically adjust the GUI according to the modules compiled into the Apache server.

These are files which are located in directories and contain configurations for the directory and directory's files - refer to the Apache documentation for more information.

To configure AccessFiles;

• Click the tab
  
  
• Enter the location of the AccessFile.
  
  
• Click the 'Use' radio button. An example of what this should look like so far:
  
  
  
  
• Click the button to use for configuration. This will be confirmed by the top tab by showing [htaccess] rather than the usual [Apache]
  
  
• You can now start setting directives as normal
  
  
• To stop using the AccessFile and go back to the main Apache settings
  
  
  • Click the tab
    
    
  • Click the 'Don't Use' radio button;
    
    
  • Click the
    
    

• Text boxes allow you to type the required information for the particular directive.
  
  
• Most values in text boxes can be enabled or disabled. If not, the value is considered a minimum command requirement for the Apache server.
  
  

Here is an example in various Look & Feel displays:

Java Metal (default)

Motif

MS Windows

This is what the settings look like in httpd.conf when the above is saved:

.... .... ServerName Enabled #NameVirtualHost Disabled ServerAdmin Permanent .... ....

• Radio buttons are simply point and click options for a command.
  
  
• Most radio buttons can be enabled or disabled, if not, the value is considered a minimum command requirement for the Apache server.
  
  

Here is an example in various Look & Feel displays:

This is what the settings look like in httpd.conf when the above is saved:

.... .... ServerSignature On #ServerTokens Minimal .... ....

• Lists allow you to enter a number of values for a single command.
  
  
• All lists can be enabled or disabled.
  
  

Here is an example in various Look & Feel displays:

This is what the settings look like in httpd.conf when the above is saved in enabled state:

.... .... IndexIgnore .??* *~ *# HEADER* README* RCS CVS *,v *,t .... ....

This is what the settings look like in httpd.conf when the above is saved in disabled state:

.... .... #IndexIgnore .??* *~ *# HEADER* README* RCS CVS *,v *,t .... ....

• Tables allow you to enter a number commands with values.
  
  
• All table entries can be enabled or disabled.
  
  

Here is an example in various look & feel displays:

This is what the settings look like in httpd.conf when the above is saved:

.... .... LoadModule mmap_static_module libexec/mod_mmap_static.so #LoadModule agent_log_module libexec/mod_log_agent.so #LoadModule mime_magic_module libexec/mod_mime_magic.so LoadModule info_module libexec/mod_info.so .... ....

Adding and Editing Values

Editing a value is done by:

• Double-clicking the value you want to change - this will allow the value to be edited.

• You can now change to the desired value.

It is the same type of principal when wanting to add new table entry. After clicking the 'Add' button, a new blank line is added to the bottom of the table, which can then be double clicked and edited:

• Used for section directives, but is likely to be used for future NetLoony tools.

Here is an example in various Look & Feel displays:

This is what the settings look like in httpd.conf when the above is saved:

.... .... <VirtualHost vserve1> <Directory dir1> </Directory> <Files file1> </Files> </VirtualHost> <VirtualHost vserve2> <Directory dir2> </Directory> <Files file2> </Files> </VirtualHost> <VirtualHost vserve3> <Directory dir3> </Directory> <Files file3> </Files> </VirtualHost> <Directory dir0> </Directory> <Files file0> </Files> .... ....