= Blueprint for Web Setup =

Provide a 1st-time configuration screen.

Setting the 1st username/password here & then running {{{models/zzz_1st_run.py}}} means that:
 * User can be given admin rights even on databases which support referential integrity.

Configuration settings are in the file {{{models/000_config.py}}} which will have a simple structured format.
 * {{{models/00_settings.py}}} reads these settings to do the actual configuration.
 * The Web Setup should ideally read in the {{{000_config.py}}} file, make any amendments as-required & then write it out.
 * This means that developers can edit the settings live (we remain RAD) & there are no unncessary DB calls every request.
 * Ideally the Web setup should have a UI which works via introspection, so doesn't need to be maintained separately when settings are added/amended (this means the settings file needs to include labels/help text).

These are the settings which will be configured:
 * Randomising the hmac_key during web setup before 1st admin password is created is important.
 * Securing the self-registration

Provide an option to import themes of settings (e.g. 'FEMA') using {{{shn_import}}} from CSV files in {{{private/import}}}:
 * Symbology (icons on maps)
 * Terminology of Labels
 * Forms used (which fields are used, which are mandatory, etc)
 * Which modules are active

Sahana2 version:
 * http://wiki.sahana.lk/doku.php?id=dev:websetup
 * http://wiki.sahana.lk/doku.php?id=dev:saws

----
BluePrints