Mise env management, module composability, and podman support#185
Open
keithy wants to merge 5 commits intonextlevelbuilder:mainfrom
Open
Mise env management, module composability, and podman support#185keithy wants to merge 5 commits intonextlevelbuilder:mainfrom
keithy wants to merge 5 commits intonextlevelbuilder:mainfrom
Conversation
keithy
changed the title
Author
|
Refined podman configuration to be an optional mise 'environment': env = "podman" |
keithy
force-pushed
the
feature/mise_n_podman
branch
from
806569c to
fcf2700
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
It was a personal crusade of mine to make docker-compose composable. (https://github.com/keithy/sprankle-pod)
When I saw this project, I felt it needed the sprankle-pod touch.
Some compose-ability can be achieved by defining COMPOSE_FILE.
Combining this approach with mise-en-place I have been able to coax goclaw to life running rootless, (i.e. in user-space), using podman, backed by the zfs filesystem.
Mise-en-place provides management of the environment variables, including various plugins for encrypting secrets.
~/.config/mise/config.toml- Users personal API KEYS (encrypted/managed by vault-plugin etc)/code/goclaw/mise/config.toml*sprankel-pod was a a joke project announcement by docker a while back