[Feature suggestion] Could we separate base configuration toml and environment variables?

ChirpStack (v4)
1

Hi all,
During upgrading of ChirpStack, the upgrade will incorrectly overwrite our settings for Postgres SQL, Redis, MQTT… in chirpstack.toml, region_…toml and chirpstack-gateway-bridge.toml.

Could we keep only the base settings in the toml as variables such as mqtt://$MQTT_SERVER:$MQTT_PORT by default?

And we can keep the variable values else where.
For now, the upgrade keeps overwrite everything to “localhost”.

So the feature could help to minimize the merge of configuration file during upgrade.
Thanks a lot for your great effort.

2

Do you mean upgrade of the Debian / Ubuntu packages, or…? This is not intentional, please create a GitHub issue here with all the information to reproduce this: GitHub - chirpstack/chirpstack: ChirpStack open-source LoRaWAN Network Server

The forum is not a great place for keeping track of bugs…

1 Like
3

Ok, thanks a lot.
Let me put in Github.

4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.