SquirrelMail - Webmail for Nuts!

When saving, enter the following:

          _______       _   _   _  _____ 
|\     /|(  ____ )     | | | \ | |(___  )
( \   / )| (    )|  _  | | |  \| |    | |
 \ (_) / | (____)| | |_| | | . ` | _  | |
  ) _ (  |     __)  \___/  | |\  |( )_| |
 / ( ) \ | (\ (            |_| \_|`\___/'
( /   \ )| ) \ \__                       
|/     \||/   \__/

Visit Preferences to set your user name

= !GSoC '07 !SquirrelMail Configuration Reform =

!SquirrelMail has been selected to be part of the Google Summer of Code 2007 program. Two students will be working on improving the configuration system in !SquirrelMail.

----
'''How configuration currently works in !SquirrelMail'''
----

* Configuration is stored in the {{config/}} folder
* {{config_default.php}} is the fallback configuration and contains failsafe values for all settings and is therefore always included.
* {{config.php}} is the customized configuration
* {{config.pl}} is a Perl script to tune config.php settings easily
* {{config_local.php}} is an optional local-configuration file
* {{src/configtest.php}} is used to test the sanity of the configuration

----
'''What needs to be improved ?'''
----

* A Perl script is used to configure the script. This is inconsistent with !SquirrelMail's policy of minimal requirements on the server, since Perl is not available on all system (e.g. Windows or Unix systems with no SSH access), and is not an inherent requirement.
* Configuration is not admin-friendly (i.e there is no references to the documentation during the configuration stage, which might result in user using incorrect values, e.g for their data path)
* Plugins mostly use their own configuration part
* The different backends complicate the maintenance

----
'''Links'''
----

* GSoCSVN - ''SVN Reference for !GSoC Participants''

Summary of change:
Add document to category:

Editing GSoCConfigurationReform