Editing the configuration file (.env) does not seem to make any difference

[universityofstuff-com]

Editing the configuration file (.env) does not seem to make any difference. I modified the file, changed the CALLSIGN=, LOCATOR=, and even the LATITUDE= and LONGITUDE=. Nothing seems to make it use those values when I connect. I have made sure to delete the cookie from my install between tests. Any advice is appreciated.

Running on the latest version of Debian, have tried both locally on the debian machine and from multiple browsers in windows on the same network.

[trancen]

All those settings are set in SETTINGS within the application.
I don't think there is a real need to update it in ,env when the SETTINGS is whats used.

What are you expecting when you modify the .env file

[universityofstuff-com]

THe program advertises that you can set that information in the .env file so that you don't have to set it every time you use a different computer or browser. I understand that for most people setting it once in their browser is enough, but some people use different browser, and multiple computers for different things, and it is nice to only have to set it once so it works from any device on your network, and will survive things like clearing your cache and cookies. I feel like if it was important enough for them to code it, it was thought to be important to more than just one person.

[accius]

profiles now exist in the settings menu you can save the settings and load them on any other machine.

[rrosson]

.env file only works if you have your docker compose either include it like so

env_file:
  - ./.env

or you define each variable in your docker-compose.yml like so under environment

environment:
  - CALLSIGN=${CALLSIGN}
  - LOCATER=${LOCATER}
  - HOST=${HOST}

Hopefully that explains it. The issue is that the docs call to use the .env file but you have to update the docker-compose.yml file for it to work for either method. This makes it something you have to move out before upgrading then re-apply your changes to the new docker-compose.yml file that was pulled during the git pull.

Some might have noticed if you have changed that file git will get grumpy and not pull the update. Not going to get into git commands here.

I have not looked to where the profiles are being stored for persistance yet as I am late in sharing the above.