3 ms·
I wish mise has better secrets management or allows for split config e.g. a repo wide config that's to be shared and a personal config that can override whateve
by Onavo 2mo ago
I wish mise has better secrets management or allows for split config e.g. a repo wide config that's to be shared and a personal config that can override whatever's necessary. It's difficult to commit mise.toml because the [env] section almost always contains sensitive variables.
- Volundr 2mo agoAre you aware of fnox by the same author? https://fnox.jdx.dev/ https://fnox.jdx.dev/
- coryplastek 2mo agomise looks in a number of places for configuration and recommends using a `mise.local.toml` file for local-only configurations: https://mise.jdx.dev/configuration.html https://mise.jdx.dev/configuration.html the same author has a separate but related project called fnox which focuses on secrets management and integrates with mise: https://fnox.jdx.dev/ https://fnox.jdx.dev/
- LeBit 2mo agoLike someone said, there is fnox by the same author for secrets. Whatever is truly local (not necessarily secrets ) should go in mise.local.toml and not be version controlled. You also have MISE_ENV if you want to manage completely different environments.
- rsyring 2mo agoI recommend mise for almost everything. But we use 1Password for secrets and I have the need to mix and match environment profiles. So I built: https://github.com/level12/env-config https://github.com/level12/env-config