Mysql connections - ISP remote connections and development to production upload setting changes

There has been some discussion regarding this topic but I cannot find any definitive answer so I will ask.

My ISP does not allow remote connections as standard to their MySql databases however remote connections can be made by alternative settings with a unique port number.

For example the website connection may use database server: sql-svr1 username: userxxxx password: passwordxxx port: 3306
however to connect remotely from wappler i have to use an alternative port, say port 5575

So my first question is how do I manage this as working within Wappler when i must use port 5575 but the live site must use port 3306.

Secondly, just to complicate thing, obviously i do not normally author and test on the live site, i develop on my local network web and mysql server. I use dns to map a domain to my local web and mysql server and this is the way I normally work.

However when i upload the site from the local server to the production server I have to manually edit the connection file with the alternative MySql connections settings.

In Dreamweaver i would simply cloak the connections folder to prevent it uploading and overwriting the server copy as the contents are only the connection settings but in wappler the entire database structure is embedded in the file so it has to be uploaded and then the settings changed.
Anyone come up with an alternative method to manually editing the dmxConnections file?
It would be useful to be able to have settings configured for local or production settings

Community Page
Last updated: