New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

accounting for mdm config: per app or per system? #11

Open

keithbentrup opened this issue Aug 29, 2020 · 0 comments

Member

keithbentrup commented Aug 29, 2020

should mdm config be per app (in app resources dir) OR per system (~/.mdm/)

end user receives the app

launcher will cause self_install to run
- can't download a global config -> no such thing b/c diff teams will have diff config
- app that contains launcher must also contain config to be distributed
- will need way to update config (for now just instructions)
if user create a new app, dockerize will copy existing one from ~/.mdm/.mdm_config.sh

dev who clones MDM

will need to create their own from the template
.mdm_config.tmpl.sh -> .mdm_config.sh (which will be .gitignored)
dev should put online and set MDM_CONFIG_URL for their fork

CI test env running tests

will download from specified env var MDM_CONFIG_URL

what if doesn't exist?

each defined var will stop something from being available or working

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment