This repository was archived by the owner on Dec 10, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 3
Profile management #15
Copy link
Copy link
Open
Labels
Description
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 😬
Reactions are currently unavailable