Hi again!
How about allowing an environment variable such as PMAMULTICONFIG that specifies what config_*.inc.php3 file should be used? That way multiple config files can be supported under the same codebase and the config file could be specified with SetEnv or in the Web Properties of whatnot.
Most of the time the "SetEnv" function is disabled on shared servers, isn't it?
Loïc
______________________________________________________________________________ ifrance.com, l'email gratuit le plus complet de l'Internet ! vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP... http://www.ifrance.com/_reloc/email.emailif
On Thu, 11 Oct 2001, Loïc wrote:
Hi again!
How about allowing an environment variable such as PMAMULTICONFIG that specifies what config_*.inc.php3 file should be used? That way multiple config files can be supported under the same codebase and the config file could be specified with SetEnv or in the Web Properties of whatnot.
Most of the time the "SetEnv" function is disabled on shared servers, isn't it?
I mean the SetEnv Apache directive, not the putenv() PHP function.
On Thu, 11 Oct 2001, Ignacio Vazquez-Abrams wrote:
I mean the SetEnv Apache directive, not the putenv() PHP function.
While the majority of us do run phpMyAdmin on Apache, there are some other servers out there as well.
On Thu, 11 Oct 2001, Robin Johnson wrote:
On Thu, 11 Oct 2001, Ignacio Vazquez-Abrams wrote:
I mean the SetEnv Apache directive, not the putenv() PHP function.
While the majority of us do run phpMyAdmin on Apache, there are some other servers out there as well.
Yes, I'm aware of that. Which is why my original post mentioned environment variables in general, not just in relation to Apache :)
How about allowing an environment variable such as PMAMULTICONFIG that specifies what config_*.inc.php3 file should be used? That way multiple config files can be supported under the same codebase and the config file could be specified with SetEnv or in the Web Properties of whatnot.
Most of the time the "SetEnv" function is disabled on shared servers, isn't it?
Right Loïc :o) And some shared hosting don't event provide telnet access ... And I think that's pma's core users, the not spoiled ones ;-)
Alain.
-
Alain Brissaud -
Ignacio Vazquez-Abrams -
Loïc -
Robin Johnson