From: Carsten K. <car...@us...> - 2003-01-14 04:59:02
|
Hi All, I'd like to discuss any plans or ideas you may have to add the configurator.php functionality together with the new config system. This might require a brand new configurator who knows, I am willing to put time in there. Instead of the current self-contained configurator, a new configurator could parse the config-dist file eliminating the need to update the configurator whenever something is added to index.php (or config-dist). The configurator would still present the admin with a locally accessible the web page for choosing all the config options, but a plugin might be possible to hook into the configurator for post-install tweaking. Then configurator outputs only the parameters which changed from those in config-dist (maybe along with minimal comments) and stores them into config-user.php. Power users can still avoid the configurator if they like, by copying what they want from config-dist and paste it into config-user themseves for manual modification. Also a pedantic request to reconsider the filename config-user.php. I have no "super" ideas yet, how about config-local? Carsten |
From: Russ M. <rm...@no...> - 2003-01-14 13:17:35
|
> I'd like to discuss any plans or ideas you may have to add the > configurator.php functionality together with the new config system. What is the issue with the configurator running the schema and setting up the DB tables? That would be a nice fix. russ |
From: Carsten K. <car...@us...> - 2003-01-14 14:19:57
|
Hi Russ, I believe an automated database setup was something the PhpWiki team just never got around to doing... it's a good idea, and off the top of my head I can't think of any reason why it couldn't be added to the configurator. :) Carsten On Tuesday, January 14, 2003, at 08:17 am, Russ Miller wrote: >> I'd like to discuss any plans or ideas you may have to add the >> configurator.php functionality together with the new config system. > > > What is the issue with the configurator running the schema and setting > up > the DB tables? That would be a nice fix. > > russ |
From: Joby W. <joby@u.washington.edu> - 2003-01-14 18:29:57
|
Sorry I've been gone for a while (holidays, other work projects). Carsten, I can help with this element as well. And config-local.php is way better than config-user.php. Moving the schema into this would be a very good idea since this would dramatically ease the install routine and make customizing the tables (for multiple wikis) much easier. My preference would be for: 1) config-valid.php (config/valid.php?) - The ultimate authority with the default values and classes to validate new values. This file would not be loaded in the normal operation of PHPWIKI -- only if a configuration routine is invoked. 2) config-dist.php (config/dist.php?) - Produced by either the web configurator or a cli configurator via the config-valid.php with the default values. 3) config-local.php (config/local.php?) - Produced by either the web configurator or a cli configurator via the config-valid.php. 4a) configurator.php (config/webconfig.php) - Web based configuration tool uses base classes in config-valid.php to produce config-dist.php and config-local.php which can be downloaded and then uploaded to the proper directory. This app can be set to show the current config-local.php settings or if greater security is desired not include those values. b) config-cli.php (config/cliconfig.php?) - CLI configuration tool uses base classes in config-valid.php to produce config-dist.php and config-local.php. Use of this file will mean that the configurators (4) will not have to use PCRE to parse the comments of the config-dist.php to come up with the potentially valid values. Alternately, if it is desired to have config-dist.php be the ultimate authority and use PRCE on the comments in config-dist.php. A config-valid.php (or perhaps config-tools.php) would be useful to hold classes used to do the PRCE parsing so that both the web and cli versions of the configurator don't have to do their own implimentation. jbw Carsten Klapp wrote: > Hi Russ, > > I believe an automated database setup was something the PhpWiki team > just never got around to doing... it's a good idea, and off the top of > my head I can't think of any reason why it couldn't be added to the > configurator. :) > > Carsten > > On Tuesday, January 14, 2003, at 08:17 am, Russ Miller wrote: > >>> I'd like to discuss any plans or ideas you may have to add the >>> configurator.php functionality together with the new config system. >> >> >> >> What is the issue with the configurator running the schema and setting up >> the DB tables? That would be a nice fix. >> >> russ > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: FREE SSL Guide from Thawte > are you planning your Web Server Security? Click here to get a FREE > Thawte SSL guide and find the answers to all your SSL security issues. > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en > _______________________________________________ > Phpwiki-talk mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwiki-talk |
From: Matti A. <ma...@ik...> - 2003-01-15 10:12:52
|
Joby Walker wrote: > Carsten, I can help with this element as well. And config-local.php is > way better than config-user.php. Another name choice might be config-site.php. m. |