We use a local database for testing, and a different connection when we deploy to the production server. It seems that Wappler is designed to manage this in that depending on what Target I select, I can configure different connection information if I click on the Connection Options button in the Database Connection.
However, when we deploy to the production site, we often (or maybe always!) seem to end up with the local connection options being written to the production server which obviously breaks the site.
I’m not sure if this is a bug (it seems like it) or if we’re doing something wrong, but I can’t see any options we are missing here.
I have experienced this bug since the first time it was released.
My solution is that when I change target, i go to any server action, open the database connection, and click save.
Then click save on server action to save linking.
Then save the server action too.
Later, when I have to change the target again, I repeat the above steps.
Wappler correctly shows the connection settings as per the current target, but it does not change the config files. So saving them manually works.
It's a little worrying that such a major bug was allowed through release 3.0 - I'd consider it major given it kills my production site each time we deploy.