Re: [phpesp-dev] soma changes

[Matthew G. <mat...@gm...>]

See below
On Sat, 2008-03-29 at 11:57 +0100, Franky Van Liedekerke wrote:
> - A default config file has been added (admin/phpESP.ini.php.default),
> your own changes should go into admin/phpESP.ini.php. The advantage is
> that new options can be added to the default file and you don't need to
> change anything to your own config file. Also a fixed part has been
> added (admin/phpESP.ini.php.fixed) containing values that should not be
> changed.
> The sequence is:
> require (phpESP.ini.php.default);
> 	==> defaults, gets overwritten every new release
> require (phpESP.ini.php);
> 	==> your own values, never gets overwritten
> require (phpESP.ini.php.fixed);
> 	==> fixed parts, you can change these, but they get overwritten
> every new release
Splitting the file in this way seems reasonable.  Wouldn't we want the
file names to be *.php, so they can't be accidentally viewable?  And
since we are renaming, I don't see any reason to keep the phpESP.ini
name.

I propose:
require (config_defaults.php);
	==> defaults, gets overwritten every new release
require (config.php);
	==> your own values, never gets overwritten
require (config_fixed.php);
	==> fixed parts, you can change these, but they get overwritten

> 
> Now I also plan an easier update:
> 1) read config files
> 2) check version of phpesp in db with the one in phpESP.ini.fixed
>         if version table in db doesn't exist
> 		==> suggest version=2.0.2, is changeable
See comment I made about the suggested version in my reply to the SVN
diff email.

> 	if version table in db exists ==> take that one
> 3) show a link to take db backup if wanted
> 4) show a link to execute the update scenario: 2.0.2==>2.0.3,
> 2.0.3==>2.0.4, ... for this, the update db scripts need to be parsed
> and the DB prefix added if needed
> 5) if update ok and tables contain no prefix: show link to script for
> prefix update, and warns it needs to be changed in the config file
> when executed
> 
> Any comments?
I like the idea of allowing DB updates inside the application, we just
need to be darn sure not to destroy anything ;-)
> 
> Franky
> 
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> phpESP-devel mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpesp-devel
-- 
Matthew Gregg <mat...@gm...>