Michal Čihař a écrit :
Hi
On Mon, 06 Feb 2006 08:36:26 -0500 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
I plan to add to the doc some instructions about how to deal with the 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 choices a user has: to download the config or to save it.
Also, after reading the forum, I wonder about our decision to remove config.inc.php from main directory. Some newbies take one of those actions:
- 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 (and point to Documentation for more info). I guess most people don't want to read so huge document...
Hmmm, I am not in favor of that, because we'll have to update at 2 places. Besides, we don't force them to read the huge document, links are clear and lead them to the Install section.
Maybe we should put a minimal config.inc.php there.
I suggest something like this:
<?php /* Put here your configuration */ ?>
I made some tests and changed my mind :). Without a config.inc.php, I think the 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 shame :)
Here I'm talking about taking care of users who download directly our kits; I wonder what integrators like various distros and XAMPP will do about this.
They can put autogenerated config file in place, as they usually have enough information to do meaningful setup.
OK.
Marc