We are exporting the env in the startup script, but when changes need to be made to the .env file, we do that manually. So we can also manually export the .env file, but need something that is resilient to human error (i.e. someone makes changes but forgets to export).
My first thought was to use inotifywait and create a bash script that does this. But I am not sure if this is the best approach. After searching online, I didn't find anyone having the same issue, so I am wondering if our approach is completely off.