Hi all
I know we stopped shipping default config file because it leads to unability to change effectively defaults. However some kind of default config is useful when you want to configure manually for whatever reason. So what about shipping some minimal default config file (as /config.default.inc.php) only with commonly used settings? I'd suggest just one server section + blowfish secret. This would hopefully prevent users blindly copying libraries/config.defaults.php.
Comments?
Michal Čihař wrote:
Hi all
I know we stopped shipping default config file because it leads to unability to change effectively defaults. However some kind of default config is useful when you want to configure manually for whatever reason. So what about shipping some minimal default config file (as /config.default.inc.php) only with commonly used settings? I'd suggest just one server section + blowfish secret. This would hopefully prevent users blindly copying libraries/config.defaults.php.
Comments?
--
that's what i supposed some weeks ago, someone said no "for security reasons". but together with auth type = cookie i can't see such danger.
No reply so far? :-)
Any objections against putting attached file into CVS?
Michal Čihař a écrit :
Hi all
I know we stopped shipping default config file because it leads to unability to change effectively defaults. However some kind of default config is useful when you want to configure manually for whatever reason. So what about shipping some minimal default config file (as /config.default.inc.php) only with commonly used settings? I'd suggest just one server section + blowfish secret. This would hopefully prevent users blindly copying libraries/config.defaults.php.
Comments?
Michal,
please wait a bit, I still have to think about this and why we had decided against.
Users who want all configuration options would still want to copy config.defaults.php.
Marc
Marc Delisle a écrit :
Michal Čihař a écrit :
Hi all
I know we stopped shipping default config file because it leads to unability to change effectively defaults. However some kind of default config is useful when you want to configure manually for whatever reason. So what about shipping some minimal default config file (as /config.default.inc.php) only with commonly used settings? I'd suggest just one server section + blowfish secret. This would hopefully prevent users blindly copying libraries/config.defaults.php.
Comments?
Michal,
please wait a bit, I still have to think about this and why we had decided against.
Users who want all configuration options would still want to copy config.defaults.php.
Marc
We would also have to deal with the issue that developers modify config.inc.php for their own use and must avoid committing it. Remember config.developer.php?
Marc
Marc Delisle wrote:
Marc Delisle a écrit :
Michal Čihař a écrit :
Hi all
I know we stopped shipping default config file because it leads to unability to change effectively defaults. However some kind of default config is useful when you want to configure manually for whatever reason. So what about shipping some minimal default config file (as /config.default.inc.php) only with commonly used settings? I'd suggest just one server section + blowfish secret. This would hopefully prevent users blindly copying libraries/config.defaults.php.
Comments?
Michal,
please wait a bit, I still have to think about this and why we had decided against.
Users who want all configuration options would still want to copy config.defaults.php.
Marc
We would also have to deal with the issue that developers modify config.inc.php for their own use and must avoid committing it. Remember config.developer.php?
Marc
Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&da... _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Michal wrote 'shipping', released version that is, not in CVS. that can't be harmful if only cookie and blowfish is included. if you have your own config , you override/edit it anyway.
On Fri, 25 Aug 2006 12:26:48 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
We would also have to deal with the issue that developers modify config.inc.php for their own use and must avoid committing it. Remember config.developer.php?
I want it as config.sample.inc.php NOT as config.inc.php.
Michal Čihař a écrit :
On Fri, 25 Aug 2006 12:26:48 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
We would also have to deal with the issue that developers modify config.inc.php for their own use and must avoid committing it. Remember config.developer.php?
I want it as config.sample.inc.php NOT as config.inc.php.
The contents of the file is ok for me. Just add, as suggested by Juergen, an additional hint near the blowfish_secret directive, because they'll all get an error message.
To better help users (that use releases and do not checkout CVS), maybe this contents could be part of create-release.sh, then generated as config.inc.php at release time?
Marc
Hi
On Sat, 26 Aug 2006 09:11:59 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
The contents of the file is ok for me. Just add, as suggested by Juergen, an additional hint near the blowfish_secret directive, because they'll all get an error message.
Okay.
To better help users (that use releases and do not checkout CVS), maybe this contents could be part of create-release.sh, then generated as config.inc.php at release time?
I don't think so, but feel free to do so.
Michal Čihař a écrit :
Hi
On Sat, 26 Aug 2006 09:11:59 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
The contents of the file is ok for me. Just add, as suggested by Juergen, an additional hint near the blowfish_secret directive, because they'll all get an error message.
Okay.
To better help users (that use releases and do not checkout CVS), maybe this contents could be part of create-release.sh, then generated as config.inc.php at release time?
I don't think so, but feel free to do so.
With a sample config file, we want to help users who do not read the doc, right? Since they expect a config.inc.php, let's give them one.
There is also my other comment about what they expect in config.inc.php. Don't you think they will still want to copy the default config file to get more options and avoid cut&paste job?
Marc
On Sun, 27 Aug 2006 08:06:20 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
With a sample config file, we want to help users who do not read the doc, right? Since they expect a config.inc.php, let's give them one.
I prefer directing them to setup when config not found, but I'm not strictly convinced it is better...
There is also my other comment about what they expect in config.inc.php. Don't you think they will still want to copy the default config file to get more options and avoid cut&paste job?
Most people do not use that much options. IMHO they simply don't read doc and need config file to be able to connect to MySQL, so they take defaults one. Now they will have one in top level directory and it should help them.
-
Jürgen Wind -
Marc Delisle -
Michal Čihař