Skip to content
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.

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

Profile management #15

Open
Wabri opened this issue May 17, 2022 · 0 comments
Open

Profile management #15

Wabri opened this issue May 17, 2022 · 0 comments
Labels
feature_request New feature request

Comments

@Wabri
Copy link
Member

Wabri commented May 17, 2022

In the old version of daje we had os_*.yml that be use as default profile if matched the os where daje was run, otherwise you can pass the -e 'profile=<profile_name>' variable to change it.

We need to consider that more profile could be used in a system or more profile could be define for a OS. Maybe use a tree like hierarchy:

profile
  |
  |-- mac
  |        |
  |        |-- main (as default configuration for mac)
  |        |
  |        |-- python (seconday configuration for mac)
  |
  |-- arch_vm1
           |
           |-- main (as default configuration for arch_vm1)
           |
           |-- javascript (seconday configuration for arch_vm1)
           |
           |-- go (third configuration for arch_vm1)

We could imagine if I want to install all profile mac I can run: daje apply mac to only apply main configuration, daje apply arch_vm1 main,go to apply a specific subset of configuration for a profile and to apply all the configuration of a profile we use daje apply mac --all.

These are just ideas, they should be argued and detailed much more 😬

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature_request New feature request
Projects
None yet
Development

No branches or pull requests

1 participant