Hello,
would it be possible to specify the configuration options in the compose file in place of the dedicated config.yaml?
distributing u2m to different machines would be far easier being able to modify only the compose (-> portainer stacks) and not also moving a config file around…
Thanks
You can do that already, so long as MQTT_HOST etc env vars are defined in the compose file or an .env file the compose file loads.
You only need the config file if need to tune any of the other config away from defaults, or don’t like the OS hostname being used
I’ve added a unit test to make sure this always happens, but didn’t need to change any of the code to make it work.
v1.5.1 has a few more env vars too, so fewer cases where it needed
So if i start from the sample config here
excluding the MQTT block (that i can replace with env vars) for all the rest i still need the config file, right? so i still need to copy the config file around 
i can survive, don’t worry
i see you changed something also in the hass_formatter file with 1.5.1, something i need to worry about?
Thanks! (please answer to me and not to the thread otherwise i can’t see your posts 
)
Recent new version brings more helpful details for more containers, including release summaries to show in the UI, and meaningful version numbers where these are provided by container builds.
Plus more options to fine tune which containers generate notifications, and ability to run this without a configuration file, using only container labels or env vars