Michal =C4=8Ciha=C5=99 a =C3=A9crit :
> On Mon, 06 Feb 2006 08:36:26 -0500
> Marc Delisle <Marc.Delisle@...> wrote:
>>I plan to add to the doc some instructions about how to deal with t=
>>config directory for users of a Windows server. They might not like=
>>being told to do "chmod" :)
> Good point ;-).
Doc modified about this. Also I added explanations about the 2 choice=
s a user=20
has: to download the config or to save it.
>>Also, after reading the forum, I wonder about our decision to remov=
>>config.inc.php from main directory. Some newbies take one of those =
>>- edit directly config.default.php
>>- complain about the product not working on a default installation
> Maybe we could write short install instructions into INSTALL file (=
> point to Documentation for more info). I guess most people don't wa=
> to read so huge document...
Hmmm, I am not in favor of that, because we'll have to update at 2 pl=
Besides, we don't force them to read the huge document, links are cle=
ar and lead=20
them to the Install section.
>>Maybe we should put a minimal config.inc.php there.
> I suggest something like this:
> /* Put here your configuration */
I made some tests and changed my mind :). Without a config.inc.php, I=
message is clear and invites the user to do the proper thing (setup).
With a minimal config.inc.php, they won't see this invitation, which =
would be a=20
>>Here I'm talking about taking care of users who download directly o=
>>kits; I wonder what integrators like various distros and XAMPP will=
> They can put autogenerated config file in place, as they usually ha=
> enough information to do meaningful setup.