Hi Christoph, > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Christoph Baudson > Sent: Tuesday, September 11, 2007 5:09 PM > To: [email protected] > Subject: Re: [Mapbender-dev] Version-number at mapbender.conf > > Hi Marko, > > your initiative is very much appreciated. I have a few suggestions > > 1) Maybe we should add an enhancement ticket in Trac >
ok, I will do that > 2) I'm not sure if you're aware that Bjoern Heuser/Christoph > Strotmann were interested in updating the setup as well. > Maybe there can be synergy. > Bjoern/Christoph: If you are reading this, please let us know > if you are still interested, and please do share your thoughts. > that would be nice! > 3) Your suggestion sounds very comfortable. However, a db web > user might not have the rights to alter the tables. We would > have to discuss if that is a problem. other projects, like joomal or sahana, have the same procedure, to install the db as web user. > > 4) What might be a problem in Mapbender is this: You can call > index.php without checking your setup previously. I believe > that it would make sense to avoid calling index.php until the > setup is ok. I have seen that in Sahana (www.sahana.lk) if > you want to take a look. had a little test yesterday evening and created a new disaster! ;-) think it is nice, but secondary. first we should create a complete installation routine before we can implement the 'setup_ok_check'. we have to discuss, what category of errors while the 'setup_ok_check' prevent of calling the index.php and which errors are negligible.... > > Thanks very much for working on Mapbender, > > Christoph > > On Tue, September 11, 2007 2:14 pm, Samson, Marko wrote: > > Hi devs, > > > > Astroid, sorry, Astrid and me just had a little > mail-conference about > > the mapbender_setup.php. > > > > Summary of our thoughts: > > For the current mapbender_setup and the further > development, it would > > be nice to have a version number at one central point, like the > > mapbender.conf. > > > > For the curent version, just for displaying it at the > mapbender_setup. > > For further version, to create a dynamic update script for the > > installed version. (for example) > > > > > > Example: > > > > 1. mapbender.conf has version 2.4.0 > > > > 2. mapbender.conf-dist has version 2.5.0 (or furture > mapbender-setup > > script has the latest version number hardcoded) > > > > 3.The future mapbender-setup update function will get the required > > database changes from a historized database-changes file > (txt,xml,json > > ...whatever?!) > > > > current version 2.4.0<->new version 2.5.0 = create an update script > > from version 2.4.1 up to 2.5.0 from database-changes file ...... > > > > <version 2.4.1 changes> > > <CREATE TABLE layer_epsg_tmp AS SELECT DISTINCT * FROM > layer_epsg;>...... > > <version 2.5.0 changes> > > <ALTER TABLE wfs_conf_element ADD COLUMN f_auth_varname > > VARCHAR(50);>...... > > > > 4. run script > > 5. and so on > > > > > > What do you think about a version number at the conf? > > What do you think about the idea for expand the mapbender_setup of > > mapbender with an update function? Any ideas or thoughts?! > > > > > > > > > > > > > > > > Greetings, > > Marko Samson > > > > > > Marko Samson > > Landesbetrieb Wald und Holz NRW > > GIS-Anwendungsentwicklung > > Referat I-5 > > Albrecht-Thaer-Straße 34 > > 48147 Münster > > > > Tel.: 0251/91797 - 169 > > Mail: [EMAIL PROTECTED] > > _______________________________________________ > > Mapbender_dev mailing list > > [email protected] > > http://lists.osgeo.org/mailman/listinfo/mapbender_dev > > > > > _______________________________________________ > Mapbender_dev mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/mapbender_dev > _______________________________________________ Mapbender_dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapbender_dev
