Is there a command line option we can pass to mattermost desktop so that it doesn’t open the program right after install? We are placing the configuration file in the %APPDATA% directory by overwriting the old one, but if the application launches before the configuration file has been updated it will not launch with the correct config.
It appears that the configuration as documented in the deployment guide doesn’t work at all.
I am using mattermost-destop-setup-4.2.2-win.exe.
Even if I quit the first start and manually delete/replace the config.json it doesn’t work. The only thing I have not tried is creating the config file first, and then installing the app.
For small to medium deployments recompiling the app is just not worth it just to change the default settings or add a default server.
I’m still waiting on a solution to this issue. For any size deployment noone should have to recompile the entire app for a setting when we have a configuration file.
AAAAAND I found it.
Invalid config files are apparently silently ignored and replaced by the default.
The trick:
Preconfigured teams need an order.
The “teams” array requires an undocumented third parameter: “order”: 0 (obviously increasing for each team you want to preconfigure).