Production DB settings as managed db and local as docker db

======== TEMPLATE BUG FORM ========

Wappler Version : 4.7
Operating System : Mac
Server Model: NodeJS
Database Type: MySql8
Hosting Type: Docker (local) AWS/Docker Remote.

Expected behavior

What do you think should happen?

I’ve noticed issues with the DB connections not finding fields etc… so I started trying to debug this by looking at the connection files.

What I notices is the docker named target (local dev) databases>db.json file is displaying the production db connection settings. This is a pretty significant issue, no telling what issues this may cause in my prod db.

I checked the target db settings and can confirm that it’s displaying as the local docker DB.

So I re-save the target and recheck the file. The db.json file has now changed to the local settings. Great. I think it’s a bug in W4 - hopefully not too many major issues to find / fix in production.

I then click ‘deploy’ as I want to fully deploy the files and check the SC action to see if it works.

It fails.

I check the db.json file and after deploying it reverts back to prod db connection settings.

@Teodor - some help please.

Update - it’s not just a redeployment that causes the overwrite, literally any alternative action. If I go back to the file, it’s been overwritten again.