Request: Map the internal SQL IP address to something like my.sql.domain.tld
-
Thinking about it, maybe @girish might have an answer for me. He taught me the tunneling technique that it appears all SQL Clients have that I just never knew about - last fall: https://forum.cloudron.io/post/13959
So maybe, Girish, do you have a solution that doesn't involve me manually changing the IP address of the "Internal MySQL Host" in my Remote SQL client every time
mysql
gets a new IP address (often)? -
-
from here - save me swearing at DBeaver periodically.
-
@girish said in Request: Map the internal SQL IP address to something like my.sql.domain.tld:
Good request. The only way I can think of is to give static IPs to all the addon containers. This is entirely doable and we haven't had a reason to hard code IPs so far. I will let this sit a bit to understand the implications of hardcoding the IPs.
Perhaps hardcoding isn't necessary, but simply using an internal DNS mapping, internal resolver for known service containers like you have in docker
OR
If you do hardcode it, use xip.io as explained here
https://forum.cloudron.io/topic/3574/xip-io-access-any-dev-app-via-internal-ip-using-a-magic-domainAlternatively, see here:
https://sslip.io/which includes a noteworthy mention of LocalTLS