Reload Server Connect Environment Settings on Remote Target?

I changed my mail provider information on my staging server in Wappler. I did this using the Server Connect Settings -> Environment tag. I pressed the Save button and restarted the services on my staging server. However, the app/config/config.json file on the staging server does not reflect the changes made and saved in Wappler (only locally do I see the changes in the staging server's config.json file). The staging server still contains the old mail provider data.

Is it possible to force a reload of the config.json file's configuration without having to do a full deploy?

In the meantime, I used the "publish" button instead of Deploy and selected just that file. This worked, but hoping there's a way to perform minor changes without taking the site down momentarily.

It's a little confusing, but the Environment settings are different for each target.
image

Try switching to your Staging target and then reopen Enviroment tab.

Yeah, that tripped me up in the past but I'm aware of that now. I had my target set to staging when updating the environment variables.

Since I use Docker, it seems the only way to have the config.json file updated on the remote target is to force a new image build. Is this correct?

When you use Publish and select the Staging server in "Publish to" field, it should make the updates.

image

It did. That was my "let's fix this now and see what the community comes back with" solution. :wink:

ah, I didn't read that comment. I know there have been conversations about zero-downtime deployment, but outside of that, making updates while using Docker requires a small amount of downtime.

1 Like