Re: [Phpwiki-talk] config in db

[Bob A. <apt...@cy...>]

Hi,

On Mon, 26 Jan 2004 09:05:49 +0100 "Oliver Betz" <ob...@de...> wrote:

> Reini Urban wrote:
> 
> > Why not storing the index.php configuration in the database, table 
> > config, editable only by the admin?
> 
> because it would be less transparent. As long as the config is in a 
> plain text file, I can:
> 
> - modify it without special tools,
> - look at it (check it) as a whole,
> - compare different configs with a text diff tool and
> - merge settings e.g. when changing more thn one Wiki.
> 
> I guess there are more reasons.

FWIW, eGroupware allows you to change its configuration from within the
application (e.g. read config.php, make changes, then save the changes
along with a backup of the original configuration.) With proper
directory permissions and good authentication this shouldn't be too
difficult.

> Hiding configs in databases is one of the the disadvantages of the 
> windows way.
> 
> As long as the config is php, one can add also special processing if 
> he/she wants.
> 
> > This is much easier to install and maybe easier to maintain then the 
> 
> Maintenance is harder, IMO.

I don't know if my experience is typical but I spend most of my effort
trying to initially configure a PHP/MySQL application. Once it's
installed and running I rarely have to mess with it (not counting
administrative tasks like setting permissions, ACLs, etc. -- but that's
not the case we're talking about here.)

> In which manner do you think the installation will be easier than 
> now?

I'd use eGroupware as an example, though I don't think PhpWiki is all
that difficult to set up compared to similar applications (try sorting
out Tiki's permissions sometime - gruesome!)

-- Bob