Why so many server connections?

Hello Wappler experts,
my name is Karl and I’m new here.

I am currently testing Wappler (trial version) and have a question regarding data connections (Server Connect).
I noticed that you have to create a new server connection for practically all possible actions. This also leads to a new connection file…
If I give my project to the client, and the client has a different database/user/host etc., how do I explain to the client that they need to adjust the multitude of connection files?

Is there something like a customer setup for these connection files?

I have been programming database applications (Desktop / Windows / SAP etc…) for 30 years.
My understanding is that I always have a confection to the database server and all queries are based on this connection.

I would be happy if someone tells me if I am doing something wrong or if I have misunderstood something. :neutral_face:

Thanks and many greetings
Karl

I have something to add:
My development server is a Synology NAS and it is connected both inside and outside (2 lan ports). 1 is outside (Fix IP and Domain), 2 is inside my LAN. The firewall is set up so that all web server services work from the outside (80, 443, 3306, 3307 (Maria DB) etc.). Internally all services are open.
In Wappler I need the internal IP to establish a successful connection to the database (e.g. 192.168.xx.xx). If I change the server connection files on the server to localhost, then no more database connections work from the outside. Why?
What do I not understand?

Community Page
Last updated: