Michal Čihař a écrit :

Hi

On Tue, 11 Apr 2006 09:20:04 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:

...

to ease installation, shouldn't we add a config.inc.php with only comments:

<?php // This is an empty config.inc.php. With this file you can connect // to localhost with user "root" and no password. // // If you are upgrading, see Documentation.html, in the Installation // section, the "Upgrading" paragraph. // // For a new installation, you can use our web-based setup script. // See Documentation.html, "Setup script". Alternatively, you can // copy libraries/config.default.php over the present config.inc.php ?>

Users are not supposed to upgrade from CVS. Maybe some do, so those would have a problem... But the majority of users would be guided.

But this breaks usage for developers who don't use empty root password.

And also introduces a potential problem of committing a personal config.inc.php.

(Or we have to go back to config.devel.inc.php).

Probably, yes.

I don't absolutely want a config.inc.php. What is important is to guide users.

What about the idea of calling the setup script when no config.inc.php is found, but add some doc links on the setup page, linking to the upgrade section and to the setup script section in the doc?

This would break the idea of default localhost with root/no password, which is maybe not bad to break anyway :)

Marc

Michal Čihař a écrit :

On Tue, 11 Apr 2006 10:01:13 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:

...

What about the idea of calling the setup script when no config.inc.php is found, but add some doc links on the setup page, linking to the upgrade section and to the setup script section in the doc?

If auth fails with no config, we point user to setup right now. What more do you want to do?

Thanks, I did not remember this. And when user clicks on the link, if the config dir does not exist he gets further links to the doc for setup script explanations; good.

So what would be missing, maybe at the first point where we tell them to use the setup script, would be a link to the upgrade section, and -- maybe -- a hint that they can copy libraries/config.default.php to config.inc.php (if we want to tell them that, but users are telling that in the forums).

Marc

Michal Čihař a écrit :

On Tue, 11 Apr 2006 10:01:13 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:

...

What about the idea of calling the setup script when no config.inc.php is found, but add some doc links on the setup page, linking to the upgrade section and to the setup script section in the doc?

If auth fails with no config, we point user to setup right now. What more do you want to do?

There is still the point of users who are looking for config.inc.php, don't read the doc and are disoriented. Ah, maybe a config.readme.txt explaning things?

Marc

Michal Čihař a écrit :

Hi

On Tue, 11 Apr 2006 11:11:04 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:

...

There is still the point of users who are looking for config.inc.php, don't read the doc and are disoriented. Ah, maybe a config.readme.txt explaning things?

Why the hell are they looking for config.inc.php?

Because this is what they did for the past 8 years?

­> Adding another

documentation for users who don't read documentation looks a bit strange to me ;-).

This would be a little bit of documentation present directly where their eyes are looking.

Marc

Garvin Hicking a écrit :

Hi!

...

to ease installation, shouldn't we add a config.inc.php with only comments:

...

Users are not supposed to upgrade from CVS. Maybe some do, so those would have a problem... But the majority of users would be guided.

But then also upgrading users via FTP would be concerned? If they just unpack a new release file over their old installation, the config.inc.php would be overwritten.

Are they really doing that? And they have no backup, right? Hmmm yes it's dangerous then. See my other message about alternatives.

Regards, Garvin