Hi I had to change the live production server target crendtials for the mysql DB connections from one server to another. However even though I have changed them, for some reason after I publish all the files, it still pointing to the old db server and getting data from there.
I have tried everyone from deleting all the files on the liver server and republished everything, but I am still getting data from the old database server.
This does happen from time-to-time. We usually kill wappler, re-start and set the DB params again. Make sure you do it in both places direct/global. It seems to arise when swapping between targets regularly and then deploying to production.
Always check after a live deployment that it’s correct when building manually from Wappler. We’ve opted to modify the docker files as part of a CI/CD model to avoid issues.
@scalaris a few questions
I’ve tried so many times re-entering the db params and its not working.
I look forward your help.
Could you kindly be more specific
2. When you say make sure it’s set in both places direct/global, is global also specific to which Target you have selected at the time? Or is global db connection just for localhost?
We reset direct connection and globals regardless
I am not sure I follow the screenshot you provided.
So essentially I have to set DB alarms four times, one for local, for live (direct connections) and then you go back and you do it from Globals? provided that Gobals is dependant on what Target. you select at the bottom?
Yes, that’s how we approach it.
Close the Wappler IDE and kill the process. Start again.
How do you start again, do you mean restart form a blank project?
Anyhow, if you are talking about restart, I did a whole shutdown and open Wappler again and it still didn’t work.
We reset direct connection and globals regardless
How do you reset? Are we deleting files, are we doing something else. Could you please be more specific
Yes, that’s how we approach it.
SO Globals is target specific??? I am not sure it is?
I understand under Database Connections, the direct connections are target specific, but not sure of Globals.
Many thanks. Look forward to your reply.
Close the Wappler IDE and kill the process. Start again.
How do you start again, do you mean restart form a blank project?
Anyhow, if you are talking about restart, I did a whole shutdown and open Wappler again and it still didn’t work.
It doesn’t always work first time.
We reset direct connection and globals regardless
How do you reset? Are we deleting files, are we doing something else. Could you please be more specific
Update with correct values
Yes, that’s how we approach it.
SO Globals is target specific??? I am not sure it is?
I understand under Database Connections, the direct connections are target specific, but not sure of Globals.
That’s what works for us - may not actually be necessary
Definitely needs to be one single unified approach to connections for databases. Still catches us out running around in circles. For a new User must be a total head…
@scalaris this is not working for us.
It’s still stuck and connecting to old settings.
@Teodor is this a bug? Changes we make to DB connection parameters for the production server are not being updated. We have values for local server and values for production, but making any changes isn’t being updated for some reason when we upload.
