As it sounds like enhancements are being made to managed database connections with DO, one part of my workflow that I have to do manually is update the connection string to include private to enable the connection over VPC. It would be great for there to be a setting that could specific leveraging the private connection string. Any time I update the project file I must manually update both mySQL and Redis connection strings.
I was just working indeed on exactly those settings.
So it seems logical to me to use the public connection settings for Wappler itself and the private one for server connect? Assuming that the server is also on digital ocean otherwise also use the public ones there?
2 Likes
Yes - that sounds correct! Anything related to Wappler connecting to get the database schema etc needs to be public, while the connection from the web app to the database should be private. And yes, the VPC only works if your docker image is hosted on the same DO VPC network as the database (e.g. nyc3, lon1). Cool you're working on this!
2 Likes
Fixed in Wappler 6.6.1
This topic was automatically closed after 14 hours. New replies are no longer allowed.