I'm not really sure should I write it in English because I speak Russian, but...
Many years ago I've used VesataCP with Remore MySQL feature. As I remember, it worked. Then I've used only local DBs for years.
Now I have
- Amazon EC2 instance
- Amazon RDS2 instance
I've installed myVesta with mysql and added v-add-database-host. Databases are created or deleted normally on both mysql servers.
But:
- I want [my]Vesta to actualize config-db.php in phpmyadmin, since default config only allows me to connect to localhost server;
- I can't connect to remote MySQL with user created from myVesta (Access denied);
- Amazon RDS' mysql - user table has only system users and admin user created with RDS, no my admin_*** user created with the database;
- When I call v-change-database-user either with password or not 2 records are added to remote user table: % and localhost with user name and EMPTY pass and auth string columns (btw Hestia behave exactly the same way);
- Adding users to remote MySQL manually is not the solution, if I wand to do it this way I don't need a panel
- Default phpmyadmin and webmail URIs are located default amazon (internal) hostname and must be changed manually
Also, IMO php-mysql, phpmyadmin etc MUST be installed regardless --mysql yes or no, or the separate parameter for these (and all related) packages should be implemented. For any multi-server configuration it would be useful to run one server with VestaCP as a frontend (with mysql client, phpmyadmin and all related) and MySQL server itself on different machine. Now phpmyadmin etc are not installed if --mysql no
P.S. I like that now v-backup-user does not fail if the localhost mysql server is down or disabled. It was the former issue that forced either to change scripts or to leave mysql server consuming RAM when it's not required at the machine.
P.S.2 is it possible to implement custom phpmyadmin and webmail path from the box as it was done with secret url in the panel? Bruteforce attacks are still performed by domain names, even if phpmyadmin is not available for http[s]://ip/ access