From MapbenderWiki

The goal of this work group is to develop a userfriendly webbased installation routine.

Contents 1 Workgroup Setup-Routine 2 Ideas 2.1 General Ideas 2.2 Steps of the Installation Routine 2.2.1 1. Check the environment 2.2.2 2. Form to enter Settings 2.2.2.1 Database 2.2.2.2 General Settings 2.2.2.3 Special Settings 2.2.3 3. Check the entered Data 2.2.4 4. Create Database 2.2.5 5. Create Mapbender.conf 2.3 Trac

Workgroup Setup-Routine

People involved in this work group:

• User:Marko Samson
• User:Christoph Baudson
• User:Marc Jansen

Ideas

General Ideas

• storing a version number, perhaps at mapbender.conf or in a db table, to be able to display at the installed version(also important to improve the error analysis) and to create an update script

 #--------------------
 #Mapbender Version
 #--------------------
 define("MB_VERSION", "2.5.0");

• using a simple form with radio/checkbox/dropdowns to create the mapbender.conf
• if /conf writable, write conf file to conf-folder. Otherwise offer a download of the file or a popup with mapbender.conf as html/textarea or whatever.
• creating a new directory /installation/ perhaps at the /tools/ directory, which contains all required scripts

• maybe the setup checker should also indicate misconfigurations in mapbender.conf
  • if there are options like CONNECTION, some users comment all, or activate too many options. Don't laugh, this happens all the time.
  • write access for tmp or log
  • preparedstatements and mysql is also a misconfiguration

• in Apache there is a "default" folder within "conf", where the original conf files remain. When you change the confs, you are generally too lazy to do backups. Maybe this solution would be better than "mapbender.conf-dist". The point is: seperate folder for user configurations, maybe the default configuration should be stored in resources?

• if there are problems w/ setup check, the red texts should be links to the wiki, where you can learn how to solve the problem

Steps of the Installation Routine

1. Check the environment

• like mapbender_setup.php checking the php configuration etc.
• exporting the data from setup-check as a text file for better error analysis such as mailing list, trac...
• perhaps a rating would make sense, to create different levels of checkresults (ok, warning, error like). Perhaps a score rating?
• check for writable mapbender.conf file or /conf/ directory to be able to create a new mapbender.conf

2. Form to enter Settings

Database

Settings, that are required to create an login to the database

• type of database
• database-server
• port
• name of the database
• databaseuser
• database password

General Settings

Settings that must be filled by the user

• directory for temporary files
• portal on/off
• login

Special Settings

Settings, that are filled with default values and can be adjusted

• prepared statements (set by default to true, if php >5.1.X ? )
• error_reporting
• characterset
• owsproxy
• server-connection
• path to modules
• mail settings
• wms monitoring
• error logging

3. Check the entered Data

• check database connection
• check integrity
• check /tmp/ writable

4. Create Database

• using the createscript from /resources/ addicted to the given specifications

5. Create Mapbender.conf

• create a mapbender.conf and write to /conf/ alternatively as download or popup textfile or whatever

Trac

http://trac.osgeo.org/mapbender/ticket/88