Preprovision native client apps
As i'm rolling out the native Windows client to a lot of users (via windows software distribution) i'd like to be able to pre-provision the app with our mattermost servers url (and maybe other settings). It would be great if the client would support some way of getting it's initial configuration for example via a config file distributed with it.
I've posted it to the windows category but i guess this would be nice (and just as easy to implement) on every platform. Mobile apps might be more difficult though.
This feature is in progress and planned to ship with Desktop App v4.0
-
Peter commented
this would be very useful, and practically a requirement if you're interested in larger customers.
we're thinking about purchasing the Enterprise Edition and would need to deploy the Windows app to 400+ users. something like this would be invaluable.
-
meilon commented
I'd like such a feature as well.
My proposal for the easy way would be:
Check if config file under app.getPath('userData') + '/config.json' exists
if not, try reading config under app.getAppPath() + '/config.json' and copy it's content to the userData one.A better way would be to check on every start (if a admin config.json exists), if the user config.json contains at least the server(s) from the admin config.json. That way, if something changes the admin could make sure everyone has at least the company server, if someone needs an external mattermost server that wouldn't be a problem. And if the name stays the same, an URL change of an existing server wouldn't be a problem, too. An optional flag could tell the app that it should overwrite all servers and settings, should the need arise.
If there will be an acceptance of a pull request for this issue, I'd be happy to code this into the app.