I guess you basically would like a way to download the complete config.inc.php, which I understand. However, because there can be various passwords (for user and controluser), I don't think it's likely we'll make this available. Sure, in some cases it's possible to see config.inc.php anyway through file system access, but in my opinion we shouldn't allow this.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It's about exporting of settings, not about the entire config.inc.php. One can already export to JSON but AFAIK this can't be plugged into config.inc.php or can it?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Olaf,
why would you want to add these settings to config.inc.php? You can always import them in Settings > Import from file and use the "Merge with current configuration" to make them permanent.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
On Sun, Dec 14, 2014 at 11:44 AM, Marc Delisle lem9@users.sf.net wrote:
Olaf,
why would you want to add these settings to config.inc.php? You can always import them in Settings > Import from file and use the "Merge with current configuration" to make them permanent.
Would it really be permanent? Where do these settings get stored in that case?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Not really, I'm just experimenting with the settings and would like to make some of them permanent, without having to setup the pMA DBs (for config storage etc).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't think that allows for a good user experience. I like to change one setting at a time, review the effects, etc. The initial setup will never be perfect and not allowing the user to save the current settings seems weird.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For a good user experience, use the phpMyAdmin configuration storage, which was designed for correct storage of "volatile" user settings. We don't intend to duplicate the configuration storage feature.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I guess you basically would like a way to download the complete config.inc.php, which I understand. However, because there can be various passwords (for user and controluser), I don't think it's likely we'll make this available. Sure, in some cases it's possible to see config.inc.php anyway through file system access, but in my opinion we shouldn't allow this.
I agree with Isaac, but maybe Olaf can clarify the goal.
It's about exporting of settings, not about the entire config.inc.php. One can already export to JSON but AFAIK this can't be plugged into config.inc.php or can it?
Oh, I get it -- the Settings tab, not config.inc.php.
Yeah, that actually does make quite a bit of sense.
Olaf,
why would you want to add these settings to config.inc.php? You can always import them in Settings > Import from file and use the "Merge with current configuration" to make them permanent.
On Sun, Dec 14, 2014 at 11:44 AM, Marc Delisle lem9@users.sf.net wrote:
Would it really be permanent? Where do these settings get stored in that case?
They are stored in the phpMyAdmin configuration storage, which is permanent.
What if I don't have that set up?
If I understand correctly your request, this is because you had settings saved in your browser storage?
Not really, I'm just experimenting with the settings and would like to make some of them permanent, without having to setup the pMA DBs (for config storage etc).
Can the settings be stored in the pMA DB?
Olaf, after a team discussion, we believe that this would duplicate the /setup interface, so we suggest that you use /setup instead.
How does /setup allow me to save the current settings to a PHP file?
The point is to use /setup to build the configuration to your liking, using almost the same interface as Settings, then use the generated config file.
I don't think that allows for a good user experience. I like to change one setting at a time, review the effects, etc. The initial setup will never be perfect and not allowing the user to save the current settings seems weird.
For a good user experience, use the phpMyAdmin configuration storage, which was designed for correct storage of "volatile" user settings. We don't intend to duplicate the configuration storage feature.
pMA conf storage is single-server.. I'd like to export it to a VCS so it can be used on multiple servers.
Does this help?
http://docs.phpmyadmin.net/en/latest/config.html?highlight=controlhost#cfg_Servers_controlhost
No, the servers have no relation to eachother.. Each has it's own pMA install and is owned by a different person.