M
manarak
Guest
Ok, I am fed up with Plesk overwriting manual settings in the config files. There is a simple solution Plesk could implement:
Make a list of all the standard config files one needs for server tweaking:
- httpd.conf
- php.ini
- mysql.conf
- vhost.conf by domain (similar to power toys)
- proftpd.conf
- smtp_psa.conf
etc...
Create a "custom admin settings" directory somewhere in /psa
In this directory store a copy of the above files.
Each time PSA is upgraded, create a .rpmsave.01 ... .rpmsave.06 (incremental with full history).
Then create a form in Plesk panel to text-edit the active config files. Each time a file is edited, a backup of the previous file is created in the directory.
Allow admin to save a file with custom name in that directory (in order to keep a current standard settings file).
With that functionality (takes about half an hour to create), it would be much more easy to keep a server correctly configured.
If Plesk doesn't do it, then it is maybe an idea for Power Toys expansion?
Make a list of all the standard config files one needs for server tweaking:
- httpd.conf
- php.ini
- mysql.conf
- vhost.conf by domain (similar to power toys)
- proftpd.conf
- smtp_psa.conf
etc...
Create a "custom admin settings" directory somewhere in /psa
In this directory store a copy of the above files.
Each time PSA is upgraded, create a .rpmsave.01 ... .rpmsave.06 (incremental with full history).
Then create a form in Plesk panel to text-edit the active config files. Each time a file is edited, a backup of the previous file is created in the directory.
Allow admin to save a file with custom name in that directory (in order to keep a current standard settings file).
With that functionality (takes about half an hour to create), it would be much more easy to keep a server correctly configured.
If Plesk doesn't do it, then it is maybe an idea for Power Toys expansion?